diff options
| author | Stefan Eßer <se@FreeBSD.org> | 2020-11-26 17:18:18 +0000 |
|---|---|---|
| committer | Stefan Eßer <se@FreeBSD.org> | 2020-11-26 17:18:18 +0000 |
| commit | 907a6834f73ccf2839853eb67a29726275ed04b4 (patch) | |
| tree | be26a5882ff196a219183e684e983bfbd23f9055 | |
| parent | 04f2650428200cc540b6f8ce803224911d47d797 (diff) | |
Notes
98 files changed, 22964 insertions, 21752 deletions
diff --git a/.gitignore b/.gitignore index fb9bc5ab6aa2..85681bf6b48e 100644 --- a/.gitignore +++ b/.gitignore @@ -9,7 +9,6 @@ bin/*bc bin/*bc.exe bin/*dc bin/*dc.exe -bin/bcl bc.old *.o *.a diff --git a/Makefile.in b/Makefile.in index 4cc653b6a5cd..53f782c02791 100644 --- a/Makefile.in +++ b/Makefile.in @@ -29,13 +29,33 @@ # .POSIX: -VERSION = 3.2.0 +VERSION = 3.1.6 SRC = %%SRC%% OBJ = %%OBJ%% GCDA = %%GCDA%% GCNO = %%GCNO%% +BC_SRC = %%BC_SRC%% +BC_OBJ = %%BC_OBJ%% +BC_GCDA = %%BC_GCDA%% +BC_GCNO = %%BC_GCNO%% + +DC_SRC = %%DC_SRC%% +DC_OBJ = %%DC_OBJ%% +DC_GCDA = %%DC_GCDA%% +DC_GCNO = %%DC_GCNO%% + +HISTORY_SRC = %%HISTORY_SRC%% +HISTORY_OBJ = %%HISTORY_OBJ%% +HISTORY_GCDA = %%HISTORY_GCDA%% +HISTORY_GCNO = %%HISTORY_GCNO%% + +RAND_SRC = %%RAND_SRC%% +RAND_OBJ = %%RAND_OBJ%% +RAND_GCDA = %%RAND_GCDA%% +RAND_GCNO = %%RAND_GCNO%% + BC_ENABLED_NAME = BC_ENABLED BC_ENABLED = %%BC_ENABLED%% DC_ENABLED_NAME = DC_ENABLED @@ -82,13 +102,6 @@ DC = dc BC_EXEC = $(BIN)/$(EXEC_PREFIX)$(BC) DC_EXEC = $(BIN)/$(EXEC_PREFIX)$(DC) -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 @@ -96,28 +109,16 @@ 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_ENABLE_LIBRARY = %%LIBRARY%% - BC_ENABLE_HISTORY = %%HISTORY%% BC_ENABLE_EXTRA_MATH_NAME = BC_ENABLE_EXTRA_MATH BC_ENABLE_EXTRA_MATH = %%EXTRA_MATH%% @@ -128,7 +129,7 @@ BC_LONG_BIT = %%LONG_BIT%% RM = rm MKDIR = mkdir -INSTALL = ./exec-install.sh +INSTALL = ./install.sh SAFE_INSTALL = ./safe-install.sh LINK = ./link.sh MANPAGE = ./manpage.sh @@ -147,7 +148,7 @@ 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) -CPPFLAGS = $(CPPFLAGS7) -DBC_ENABLE_HISTORY=$(BC_ENABLE_HISTORY) -DBC_ENABLE_LIBRARY=$(BC_ENABLE_LIBRARY) +CPPFLAGS = $(CPPFLAGS7) -DBC_ENABLE_HISTORY=$(BC_ENABLE_HISTORY) CFLAGS = $(CPPFLAGS) %%CPPFLAGS%% %%CFLAGS%% LDFLAGS = %%LDFLAGS%% @@ -156,24 +157,21 @@ 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 +BC_LIB_C_ARGS = bc_lib bc.h bc_lib_name $(BC_ENABLED_NAME) 1 +BC_LIB2_C_ARGS = bc_lib2 bc.h bc_lib2_name "$(BC_ENABLED_NAME) && $(BC_ENABLE_EXTRA_MATH_NAME)" 1 -OBJS = $(BC_HELP_O) $(DC_HELP_O) $(BC_LIB_O) $(BC_LIB2_O) $(OBJ) -OBJ_TARGETS = $(DC_HELP_O) $(BC_HELP_O) $(BC_LIB_O) $(BC_LIB2_O) $(OBJ) +OBJS1 = $(OBJ) $(DC_OBJ) $(BC_OBJ) $(HISTORY_OBJ) $(RAND_OBJ) $(BC_HELP_O) $(DC_HELP_O) +OBJS = $(OBJS1) $(BC_LIB_O) $(BC_LIB2_O) $(BC_LIB3_O) +OBJ_TARGETS1 = $(DC_HELP_O) $(BC_HELP_O) $(BC_LIB_O) $(BC_LIB2_O) $(BC_LIB3_O) +OBJ_TARGETS = $(OBJ_TARGETS1) $(BC_OBJ) $(DC_OBJ) $(HISTORY_OBJ) $(RAND_OBJ) $(OBJ) .c.o: $(CC) $(CFLAGS) -o $@ -c $< -all: %%ALL_PREREQ%% - -execs: make_bin $(OBJ_TARGETS) +all: make_bin $(OBJ_TARGETS) $(CC) $(CFLAGS) $(OBJS) $(LDFLAGS) -o $(EXEC) %%LINK%% -library: make_bin $(OBJ) $(BC_LIB_O) $(BC_LIB2_O) - ar -r -cu $(LIBBC) $(BC_LIB_O) $(BC_LIB2_O) $(OBJ) - $(GEN_EXEC): %%GEN_EXEC_TARGET%% @@ -184,10 +182,10 @@ $(BC_LIB2_C): $(GEN_EXEC) $(BC_LIB2) $(GEN_EMU) $(GEN_EXEC) $(BC_LIB2) $(BC_LIB2_C) $(BC_LIB2_C_ARGS) $(BC_HELP_C): $(GEN_EXEC) $(BC_HELP) - $(GEN_EMU) $(GEN_EXEC) $(BC_HELP) $(BC_HELP_C) bc_help "" $(BC_ENABLED_NAME) + $(GEN_EMU) $(GEN_EXEC) $(BC_HELP) $(BC_HELP_C) bc_help bc.h "" $(BC_ENABLED_NAME) $(DC_HELP_C): $(GEN_EXEC) $(DC_HELP) - $(GEN_EMU) $(GEN_EXEC) $(DC_HELP) $(DC_HELP_C) dc_help "" $(DC_ENABLED_NAME) + $(GEN_EMU) $(GEN_EXEC) $(DC_HELP) $(DC_HELP_C) dc_help dc.h "" $(DC_ENABLED_NAME) make_bin: $(MKDIR) -p $(BIN) @@ -224,7 +222,7 @@ help: check: test -test: %%TESTS%% +test: test_bc timeconst test_dc test_bc: %%BC_TEST%% @@ -243,12 +241,6 @@ time_test_dc: timeconst: %%TIMECONST%% -library_test: library - $(CC) $(CFLAGS) $(BCL_TEST_C) $(LIBBC) -o $(BCL_TEST) - -test_library: library_test - $(BCL_TEST) - valgrind: valgrind_bc valgrind_dc valgrind_bc: @@ -280,7 +272,6 @@ extra_math: manpages: $(MANPAGE) bc $(MANPAGE) dc - $(MANPAGE) bcl clean_gen: @$(RM) -f $(GEN_EXEC) @@ -288,6 +279,10 @@ clean_gen: clean:%%CLEAN_PREREQS%% @printf 'Cleaning files...\n' @$(RM) -f $(OBJ) + @$(RM) -f $(BC_OBJ) + @$(RM) -f $(DC_OBJ) + @$(RM) -f $(HISTORY_OBJ) + @$(RM) -f $(RAND_OBJ) @$(RM) -f $(BC_EXEC) @$(RM) -f $(DC_EXEC) @$(RM) -fr $(BIN) @@ -348,20 +343,9 @@ install_bc_manpage: 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:%%INSTALL_LOCALES_PREREQS%%%%INSTALL_PREREQS%% $(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) @@ -377,13 +361,4 @@ uninstall_dc_manpage: 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%% @@ -1,23 +1,5 @@ # News -## 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 diff --git a/README.md b/README.md index cea5d877b95c..8aacb21b004c 100644 --- a/README.md +++ b/README.md @@ -107,23 +107,6 @@ 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 - -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`. - ### Package and Distro Maintainers #### Recommended Compiler @@ -352,4 +335,3 @@ Folders: [23]: https://svnweb.freebsd.org/base/head/contrib/bc/ [24]: https://bugs.freebsd.org/ [25]: https://reviews.freebsd.org/ -[26]: ./manuals/bcl.3.md diff --git a/configure.sh b/configure.sh index b41bee445594..9490787ffa21 100755 --- a/configure.sh +++ b/configure.sh @@ -45,27 +45,22 @@ usage() { _usage_val=0 fi - printf 'usage:\n' - printf ' %s -h\n' "$script" - printf ' %s --help\n' "$script" - printf ' %s [-a|-bD|-dB|-c] [-EfgGHlMNPT] [-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 'usage: %s -h\n' "$script" + printf ' %s --help\n' "$script" + printf ' %s [-bD|-dB|-c] [-EfgGHlMNPT] [-O OPT_LEVEL] [-k KARATSUBA_LEN]\n' "$script" + printf ' %s \\\n' "$script" + printf ' [--bc-only --disable-dc|--dc-only --disable-bc|--coverage] \\\n' + printf ' [--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 ' [--force] \\\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 ' Build bc only. It is an error if "-d", "--dc-only", "-B", or "--disable-bc"\n' + printf ' 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' @@ -74,10 +69,10 @@ usage() { 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 ' -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 ' Build dc only. It is an error if "-b", "--bc-only", "-D", or "--disable-dc"\n' + printf ' 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 ' 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' @@ -127,14 +122,8 @@ usage() { 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 ' The directory to install binaries. 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' @@ -147,9 +136,6 @@ usage() { 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' @@ -171,18 +157,12 @@ usage() { 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 ' BINDIR The directory to install binaries. Default is "$PREFIX/bin".\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' @@ -277,55 +257,56 @@ replace() { substring_replace "$_replace_str" "%%$_replace_needle%%" "$_replace_replacement" } -gen_file_list() { +gen_file_lists() { - if [ "$#" -lt 1 ]; then + if [ "$#" -lt 3 ]; then err_exit "Invalid number of args to $0" fi - _gen_file_list_contents="$1" + _gen_file_lists_contents="$1" shift - p=$(pwd) - - cd "$scriptdir" - - if [ "$#" -ge 1 ]; then + _gen_file_lists_filedir="$1" + shift - while [ "$#" -ge 1 ]; do - a="$1" - shift - args="$args ! -wholename src/${a}" - done + _gen_file_lists_typ="$1" + shift + # If there is an extra argument, and it + # is zero, we keep the file lists empty. + if [ "$#" -gt 0 ]; then + _gen_file_lists_use="$1" else - args="-print" + _gen_file_lists_use="1" 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_lists_needle_src="${_gen_file_lists_typ}SRC" + _gen_file_lists_needle_obj="${_gen_file_lists_typ}OBJ" + _gen_file_lists_needle_gcda="${_gen_file_lists_typ}GCDA" + _gen_file_lists_needle_gcno="${_gen_file_lists_typ}GCNO" - _gen_file_list_replacement=$(find src/ -depth -name "*.c" $args | tr '\n' ' ') - _gen_file_list_contents=$(replace "$_gen_file_list_contents" \ - "$_gen_file_list_needle_src" "$_gen_file_list_replacement") + if [ "$_gen_file_lists_use" -ne 0 ]; then - _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_lists_replacement=$(cd "$_gen_file_lists_filedir" && find . ! -name . -prune -name "*.c" | cut -d/ -f2 | sed "s@^@$_gen_file_lists_filedir/@g" | tr '\n' ' ') + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_src" "$_gen_file_lists_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_lists_replacement=$(replace_exts "$_gen_file_lists_replacement" "c" "o") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_obj" "$_gen_file_lists_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") + _gen_file_lists_replacement=$(replace_exts "$_gen_file_lists_replacement" "o" "gcda") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_gcda" "$_gen_file_lists_replacement") - cd "$p" + _gen_file_lists_replacement=$(replace_exts "$_gen_file_lists_replacement" "gcda" "gcno") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_gcno" "$_gen_file_lists_replacement") - printf '%s\n' "$_gen_file_list_contents" + else + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_src" "") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_obj" "") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_gcda" "") + _gen_file_lists_contents=$(replace "$_gen_file_lists_contents" "$_gen_file_lists_needle_gcno" "") + fi + + printf '%s\n' "$_gen_file_lists_contents" } bc_only=0 @@ -343,12 +324,10 @@ prompt=1 force=0 strip_bin=1 all_locales=0 -library=0 -while getopts "abBcdDEfgGhHk:lMNO:PST-" opt; do +while getopts "bBcdDEfgGhHk:lMNO:PST-" opt; do case "$opt" in - a) library=1 ;; b) bc_only=1 ;; B) dc_only=1 ;; c) coverage=1 ;; @@ -373,7 +352,6 @@ while getopts "abBcdDEfgGhHk:lMNO:PST-" opt; do LONG_OPTARG="${arg#*=}" case $arg in help) usage ;; - library) library=1 ;; bc-only) bc_only=1 ;; dc-only) dc_only=1 ;; coverage) coverage=1 ;; @@ -393,20 +371,6 @@ while getopts "abBcdDEfgGhHk:lMNO:PST-" opt; do 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 @@ -435,13 +399,6 @@ while getopts "abBcdDEfgGhHk:lMNO:PST-" opt; do 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 @@ -497,12 +454,6 @@ 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" ;; (*) ;; @@ -578,8 +529,6 @@ 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)" bc_time_test="@tests/all.sh bc $extra_math 1 $generate_tests 1 \$(BC_EXEC)" @@ -618,8 +567,7 @@ if [ "$bc_only" -eq 1 ]; then dc_time_test="@printf 'No dc tests to run\\\\n'" vg_dc_test="@printf 'No dc tests to run\\\\n'" - install_prereqs=" install_execs" - install_man_prereqs=" install_bc_manpage" + install_prereqs=" install_bc_manpage" uninstall_prereqs=" uninstall_bc" uninstall_man_prereqs=" uninstall_bc_manpage" @@ -642,8 +590,7 @@ elif [ "$dc_only" -eq 1 ]; then timeconst="@printf 'timeconst cannot be run because bc is not built\\\\n'" - install_prereqs=" install_execs" - install_man_prereqs=" install_dc_manpage" + install_prereqs=" install_dc_manpage" uninstall_prereqs=" uninstall_dc" uninstall_man_prereqs=" uninstall_dc_manpage" @@ -659,18 +606,9 @@ else 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 + install_prereqs=" install_bc_manpage install_dc_manpage" + uninstall_prereqs=" uninstall_bc uninstall_dc" + uninstall_man_prereqs=" uninstall_bc_manpage uninstall_dc_manpage" fi @@ -726,14 +664,6 @@ 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" @@ -754,25 +684,11 @@ if [ "$install_manpages" -ne 0 ]; then MAN1DIR="$MANDIR/man1" fi - if [ -z "${MAN3DIR+set}" ]; then - MAN3DIR="$MANDIR/man3" - fi - else - install_man_prereqs="" + install_prereqs="" uninstall_man_prereqs="" fi -if [ "$library" -ne 0 ]; then - extra_math=1 - nls=0 - hist=0 - prompt=0 - ALL_PREREQ="library" -else - ALL_PREREQ="execs" -fi - if [ "$nls" -ne 0 ]; then set +e @@ -860,11 +776,11 @@ if [ "$hist" -eq 1 ]; then 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_NLS=$nls" 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 + "$CC" $CPPFLAGS $CFLAGS $flags -c "src/history/history.c" -o "$scriptdir/history.o" > /dev/null 2>&1 err="$?" @@ -888,11 +804,7 @@ if [ "$hist" -eq 1 ]; then fi -if [ "$library" -eq 1 ]; then - bc_lib="" -fi - -if [ "$extra_math" -eq 1 ] && [ "$bc" -ne 0 ] && [ "$library" -eq 0 ]; then +if [ "$extra_math" -eq 1 ] && [ "$bc" -ne 0 ]; then BC_LIB2_O="\$(GEN_DIR)/lib2.o" else BC_LIB2_O="" @@ -934,33 +846,6 @@ if [ "$manpage_args" = "" ]; then manpage_args="A" fi -unneeded="" - -if [ "$hist" -eq 0 ]; then - unneeded="$unneeded history.c" -fi - -if [ "$bc" -eq 0 ]; then - unneeded="$unneeded bc.c bc_lex.c bc_parse.c" -fi - -if [ "$dc" -eq 0 ]; then - unneeded="$unneeded dc.c dc_lex.c dc_parse.c" -fi - -if [ "$extra_math" -eq 0 ]; then - unneeded="$unneeded rand.c" -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" -else - unneeded="$unneeded library.c" -fi - # Print out the values; this is for debugging. if [ "$bc" -ne 0 ]; then printf 'Building bc\n' @@ -973,7 +858,6 @@ 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" @@ -989,13 +873,10 @@ 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" @@ -1011,17 +892,16 @@ replacement='*** WARNING: Autogenerated from Makefile.in. DO NOT MODIFY ***' contents=$(replace "$contents" "$needle" "$replacement") -if [ "$unneeded" = "" ]; then - contents=$(gen_file_list "$contents" "library.c") -else - contents=$(gen_file_list "$contents" $unneeded) -fi +contents=$(gen_file_lists "$contents" "$scriptdir/src" "") +contents=$(gen_file_lists "$contents" "$scriptdir/src/bc" "BC_" "$bc") +contents=$(gen_file_lists "$contents" "$scriptdir/src/dc" "DC_" "$dc") +contents=$(gen_file_lists "$contents" "$scriptdir/src/history" "HISTORY_" "$hist") +contents=$(gen_file_lists "$contents" "$scriptdir/src/rand" "RAND_" "$extra_math") contents=$(replace "$contents" "BC_ENABLED" "$bc") contents=$(replace "$contents" "DC_ENABLED" "$dc") contents=$(replace "$contents" "LINK" "$link") -contents=$(replace "$contents" "LIBRARY" "$library") contents=$(replace "$contents" "HISTORY" "$hist") contents=$(replace "$contents" "EXTRA_MATH" "$extra_math") contents=$(replace "$contents" "NLS" "$nls") @@ -1037,10 +917,7 @@ 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") @@ -1050,19 +927,15 @@ 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" "ALL_PREREQ" "$ALL_PREREQ") - 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" "BC_TIME_TEST" "$bc_time_test") diff --git a/gen/lib.bc b/gen/lib.bc index 7768eb74bad1..93ac29546beb 100644 --- a/gen/lib.bc +++ b/gen/lib.bc @@ -173,7 +173,7 @@ define a(x){ return((m*a+r)/n) } define j(n,x){ - auto b,s,o,a,i,r,v,f + auto b,s,o,a,i,v,f b=ibase ibase=A s=scale diff --git a/gen/strgen.c b/gen/strgen.c index 0b2306152874..f4c4b51d1248 100644 --- a/gen/strgen.c +++ b/gen/strgen.c @@ -45,14 +45,13 @@ static const char* const bc_gen_header = "// Copyright (c) 2018-2020 Gavin D. Howard and contributors.\n" "// Licensed under the 2-clause BSD license.\n" - "// *** AUTOMATICALLY GENERATED FROM %s. DO NOT MODIFY. ***\n\n"; + "// *** AUTOMATICALLY GENERATED FROM %s. DO NOT MODIFY. ***\n"; +static const char* const bc_gen_include = "#include <%s>\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) @@ -63,7 +62,7 @@ static const char* const bc_gen_name_extern = "extern const char %s[];\n\n"; int main(int argc, char *argv[]) { FILE *in, *out; - char *label, *define, *name; + char *label, *define, *name, *include; int c, count, slashes, err = IO_ERR; bool has_label, has_define, remove_tabs; @@ -73,14 +72,15 @@ int main(int argc, char *argv[]) { } name = argv[3]; + include = argv[4]; - has_label = (argc > 4 && strcmp("", argv[4]) != 0); - label = has_label ? argv[4] : ""; + has_label = (argc > 5 && strcmp("", argv[5]) != 0); + label = has_label ? argv[5] : ""; - has_define = (argc > 5 && strcmp("", argv[5]) != 0); - define = has_define ? argv[5] : ""; + has_define = (argc > 6 && strcmp("", argv[6]) != 0); + define = has_define ? argv[6] : ""; - remove_tabs = (argc > 6); + remove_tabs = (argc > 7); in = fopen(argv[1], "r"); if (!in) return INVALID_INPUT_FILE; @@ -89,9 +89,8 @@ int main(int argc, char *argv[]) { 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 (fprintf(out, bc_gen_include, include) < 0) goto err; if (has_label && fprintf(out, bc_gen_label, label, argv[1]) < 0) goto err; if (fprintf(out, bc_gen_name, name) < 0) goto err; diff --git a/gen/strgen.sh b/gen/strgen.sh index 53acece8c06c..f389c12c0579 100755 --- a/gen/strgen.sh +++ b/gen/strgen.sh @@ -50,7 +50,6 @@ exec > "$output" if [ -n "$label" ]; then nameline="const char *${label} = \"${input}\";" - labelexternline="extern const char *${label};" fi if [ -n "$define" ]; then @@ -65,14 +64,11 @@ if [ -n "$remove_tabs" ]; then fi cat<<EOF -// Copyright (c) 2018-2020 Gavin D. Howard and contributors. // Licensed under the 2-clause BSD license. // *** AUTOMATICALLY GENERATED FROM ${input}. DO NOT MODIFY. *** ${condstart} -$labelexternline - -extern const char $name[]; +#include <${header}> $nameline diff --git a/include/file.h b/include/file.h index 6fa08b3f436c..0ba8caa80c98 100644 --- a/include/file.h +++ b/include/file.h @@ -62,4 +62,6 @@ 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_ultoa(unsigned long long val, char buf[BC_FILE_ULL_LENGTH]); + #endif // BC_FILE_H diff --git a/include/lex.h b/include/lex.h index ff9592b6e928..68b72a7f59bb 100644 --- a/include/lex.h +++ b/include/lex.h @@ -43,8 +43,8 @@ #include <vector.h> #include <lang.h> -#define bc_lex_err(l, e) (bc_vm_handleError((e), (l)->line)) -#define bc_lex_verr(l, e, ...) (bc_vm_handleError((e), (l)->line, __VA_ARGS__)) +#define bc_lex_err(l, e) (bc_vm_error((e), (l)->line)) +#define bc_lex_verr(l, e, ...) (bc_vm_error((e), (l)->line, __VA_ARGS__)) #if BC_ENABLED diff --git a/include/num.h b/include/num.h index 4868ae3de6a8..239daf908834 100644 --- a/include/num.h +++ b/include/num.h @@ -45,7 +45,6 @@ #include <status.h> #include <vector.h> -#include <bcl.h> #ifndef BC_ENABLE_EXTRA_MATH #define BC_ENABLE_EXTRA_MATH (1) @@ -55,10 +54,25 @@ typedef unsigned long ulong; -typedef BclBigDig BcBigDig; +// 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 int_least32_t BcDig; +typedef uint64_t BcBigDig; + #define BC_NUM_BIGDIG_MAX ((BcBigDig) UINT64_MAX) #define BC_BASE_DIGS (9) @@ -66,10 +80,11 @@ typedef BclBigDig BcBigDig; #define BC_NUM_BIGDIG_C UINT64_C -typedef int_least32_t BcDig; - #elif BC_LONG_BIT >= 32 +typedef int_least16_t BcDig; +typedef uint32_t BcBigDig; + #define BC_NUM_BIGDIG_MAX ((BcBigDig) UINT32_MAX) #define BC_BASE_DIGS (4) @@ -77,8 +92,6 @@ typedef int_least32_t BcDig; #define BC_NUM_BIGDIG_C UINT32_C -typedef int_least16_t BcDig; - #else #error BC_LONG_BIT must be at least 32 @@ -93,6 +106,7 @@ typedef struct BcNum { size_t scale; size_t len; size_t cap; + bool neg; } BcNum; #if BC_ENABLE_EXTRA_MATH @@ -136,30 +150,6 @@ struct BcRNG; #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 @@ -193,7 +183,7 @@ 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); + 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 @@ -210,34 +200,28 @@ 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); -bool bc_num_strValid(const char *restrict val); -void bc_num_parse(BcNum *restrict n, const char *restrict val, BcBigDig base); +void bc_num_parse(BcNum *restrict n, const char *restrict val, + BcBigDig base, bool letter); void bc_num_print(BcNum *restrict n, BcBigDig base, bool newline); #if DC_ENABLED void bc_num_stream(BcNum *restrict n, BcBigDig base); @@ -254,8 +238,6 @@ 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/include/parse.h b/include/parse.h index 7f59885346dc..a568fab13e64 100644 --- a/include/parse.h +++ b/include/parse.h @@ -62,9 +62,8 @@ #define bc_parse_push(p, i) (bc_vec_pushByte(&(p)->func->code, (uchar) (i))) #define bc_parse_pushIndex(p, idx) (bc_vec_pushIndex(&(p)->func->code, (idx))) -#define bc_parse_err(p, e) (bc_vm_handleError((e), (p)->l.line)) -#define bc_parse_verr(p, e, ...) \ - (bc_vm_handleError((e), (p)->l.line, __VA_ARGS__)) +#define bc_parse_err(p, e) (bc_vm_error((e), (p)->l.line)) +#define bc_parse_verr(p, e, ...) (bc_vm_error((e), (p)->l.line, __VA_ARGS__)) typedef struct BcParseNext { uchar len; @@ -111,7 +110,7 @@ void bc_parse_updateFunc(BcParse *p, size_t fidx); void bc_parse_pushName(const BcParse* p, char *name, bool var); void bc_parse_text(BcParse *p, const char *text); -extern const char bc_parse_zero[2]; -extern const char bc_parse_one[2]; +extern const char bc_parse_zero[]; +extern const char bc_parse_one[]; #endif // BC_PARSE_H diff --git a/include/rand.h b/include/rand.h index a2fb713803ee..3c8aafd62ade 100644 --- a/include/rand.h +++ b/include/rand.h @@ -223,7 +223,6 @@ void bc_rand_seed(BcRNG *r, ulong state1, ulong state2, ulong inc1, ulong inc2); void bc_rand_push(BcRNG *r); void bc_rand_pop(BcRNG *r, bool reset); void bc_rand_getRands(BcRNG *r, BcRand *s1, BcRand *s2, BcRand *i1, BcRand *i2); -void bc_rand_srand(BcRNGData *rng); extern const BcRandState bc_rand_multiplier; diff --git a/include/status.h b/include/status.h index 762ff3e25c36..279edfef8710 100644 --- a/include/status.h +++ b/include/status.h @@ -46,8 +46,6 @@ #define DC_ENABLED (1) #endif // DC_ENABLED -#include <bcl.h> - typedef enum BcStatus { BC_STATUS_SUCCESS = 0, @@ -60,75 +58,75 @@ typedef enum BcStatus { } 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, +typedef enum BcError { + + BC_ERROR_MATH_NEGATIVE, + BC_ERROR_MATH_NON_INTEGER, + BC_ERROR_MATH_OVERFLOW, + BC_ERROR_MATH_DIVIDE_BY_ZERO, + + BC_ERROR_FATAL_ALLOC_ERR, + BC_ERROR_FATAL_IO_ERR, + BC_ERROR_FATAL_FILE_ERR, + BC_ERROR_FATAL_BIN_FILE, + BC_ERROR_FATAL_PATH_DIR, + BC_ERROR_FATAL_OPTION, + BC_ERROR_FATAL_OPTION_NO_ARG, + BC_ERROR_FATAL_OPTION_ARG, + + BC_ERROR_EXEC_IBASE, + BC_ERROR_EXEC_OBASE, + BC_ERROR_EXEC_SCALE, + BC_ERROR_EXEC_READ_EXPR, + BC_ERROR_EXEC_REC_READ, + BC_ERROR_EXEC_TYPE, + + BC_ERROR_EXEC_STACK, + + BC_ERROR_EXEC_PARAMS, + BC_ERROR_EXEC_UNDEF_FUNC, + BC_ERROR_EXEC_VOID_VAL, + + BC_ERROR_PARSE_EOF, + BC_ERROR_PARSE_CHAR, + BC_ERROR_PARSE_STRING, + BC_ERROR_PARSE_COMMENT, + BC_ERROR_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, + BC_ERROR_PARSE_EXPR, + BC_ERROR_PARSE_EMPTY_EXPR, + BC_ERROR_PARSE_PRINT, + BC_ERROR_PARSE_FUNC, + BC_ERROR_PARSE_ASSIGN, + BC_ERROR_PARSE_NO_AUTO, + BC_ERROR_PARSE_DUP_LOCAL, + BC_ERROR_PARSE_BLOCK, + BC_ERROR_PARSE_RET_VOID, + BC_ERROR_PARSE_REF_VAR, + + BC_ERROR_POSIX_NAME_LEN, + BC_ERROR_POSIX_COMMENT, + BC_ERROR_POSIX_KW, + BC_ERROR_POSIX_DOT, + BC_ERROR_POSIX_RET, + BC_ERROR_POSIX_BOOL, + BC_ERROR_POSIX_REL_POS, + BC_ERROR_POSIX_MULTIREL, + BC_ERROR_POSIX_FOR, + BC_ERROR_POSIX_EXP_NUM, + BC_ERROR_POSIX_REF, + BC_ERROR_POSIX_VOID, + BC_ERROR_POSIX_BRACE, #endif // BC_ENABLED - BC_ERR_NELEMS, + BC_ERROR_NELEMS, #if BC_ENABLED - BC_ERR_POSIX_START = BC_ERR_POSIX_NAME_LEN, - BC_ERR_POSIX_END = BC_ERR_POSIX_BRACE, + BC_ERROR_POSIX_START = BC_ERROR_POSIX_NAME_LEN, + BC_ERROR_POSIX_END = BC_ERROR_POSIX_BRACE, #endif // BC_ENABLED -} BcErr; +} BcError; #define BC_ERR_IDX_MATH (0) #define BC_ERR_IDX_PARSE (1) @@ -165,12 +163,6 @@ typedef enum BcErr { #define BC_MUST_RETURN #endif // __STDC_VERSION__ -#if defined(__clang__) || defined(__GNUC__) -#define BC_FALLTHROUGH __attribute__((fallthrough)); -#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__ diff --git a/include/vector.h b/include/vector.h index fdfb85d58228..bad178eede30 100644 --- a/include/vector.h +++ b/include/vector.h @@ -62,7 +62,6 @@ typedef struct BcVec { void bc_vec_init(BcVec *restrict v, size_t esize, BcVecFree dtor); void bc_vec_expand(BcVec *restrict v, size_t req); -void bc_vec_grow(BcVec *restrict v, size_t n); void bc_vec_npop(BcVec *restrict v, size_t n); void bc_vec_npopAt(BcVec *restrict v, size_t n, size_t idx); diff --git a/include/vm.h b/include/vm.h index 72a5150266a1..f178c0390853 100644 --- a/include/vm.h +++ b/include/vm.h @@ -36,7 +36,6 @@ #ifndef BC_VM_H #define BC_VM_H -#include <assert.h> #include <stddef.h> #include <limits.h> @@ -57,10 +56,7 @@ #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 @@ -95,8 +91,6 @@ #define isatty _isatty #endif // _WIN32 -#if !BC_ENABLE_LIBRARY - #if DC_ENABLED #define DC_FLAG_X (UINTMAX_C(1)<<0) #endif // DC_ENABLED @@ -155,8 +149,6 @@ #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)) @@ -278,75 +270,31 @@ #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_vm_err(e) (bc_vm_error((e), 0)) +#define bc_vm_verr(e, ...) (bc_vm_error((e), 0, __VA_ARGS__)) #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; @@ -357,11 +305,9 @@ typedef struct BcVm { bool no_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; @@ -379,27 +325,21 @@ typedef struct BcVm { const char *func_header; const char *err_ids[BC_ERR_IDX_NELEMS + BC_ENABLED]; - const char *err_msgs[BC_ERR_NELEMS]; + const char *err_msgs[BC_ERROR_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; @@ -409,16 +349,13 @@ typedef struct BcVm { 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); void bc_vm_printf(const char *fmt, ...); void bc_vm_putchar(int c); @@ -434,11 +371,7 @@ void bc_vm_jmp(const char *f); void bc_vm_jmp(void); #endif // BC_DEBUG_CODE -#if BC_ENABLE_LIBRARY -void bc_vm_handleError(BcErr e); -#else // BC_ENABLE_LIBRARY -void bc_vm_handleError(BcErr e, size_t line, ...); -#endif // BC_ENABLE_LIBRARY +void bc_vm_error(BcError e, size_t line, ...); extern const char bc_copyright[]; extern const char* const bc_err_line; diff --git a/manpage.sh b/manpage.sh index edde671da238..631d162d51c3 100755 --- a/manpage.sh +++ b/manpage.sh @@ -32,21 +32,6 @@ usage() { 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" - -} - gen_manpage() { _gen_manpage_args="$1" @@ -99,7 +84,10 @@ gen_manpage() { IFS="$_gen_manpage_ifs" - print_manpage "$_gen_manpage_md" "$_gen_manpage_out" + cat "$manualsdir/header.txt" > "$_gen_manpage_out" + cat "$manualsdir/header_${manpage}.txt" >> "$_gen_manpage_out" + + pandoc -f markdown -t man "$_gen_manpage_md" >> "$_gen_manpage_out" } set -e @@ -120,12 +108,6 @@ 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 +for a in $ARGS; do + gen_manpage "$a" +done diff --git a/manuals/bc.1.md.in b/manuals/bc.1.md.in index efc0be037526..80892e742345 100644 --- a/manuals/bc.1.md.in +++ b/manuals/bc.1.md.in @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -477,9 +477,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that {{ 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**. +**\<number\>e\<integer\>**. The power (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. @@ -652,7 +652,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1019,8 +1019,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1800,7 +1798,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/A.1 b/manuals/bc/A.1 index 2e2816290587..f0966ba9d877 100644 --- a/manuals/bc/A.1 +++ b/manuals/bc/A.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,13 +44,13 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] bc(1), including (and especially) the GNU bc(1). It also has many extensions and extra features beyond other implementations. @@ -60,9 +58,9 @@ implementations. .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -70,40 +68,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -114,115 +112,118 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -231,61 +232,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -293,392 +294,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -686,264 +683,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -953,152 +956,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1107,23 +1110,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1131,528 +1134,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1664,55 +1684,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1725,7 +1745,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1733,238 +1753,269 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1972,65 +2023,65 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -2038,4 +2089,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/A.1.md b/manuals/bc/A.1.md index 5e5b75bb3821..e67c20656e23 100644 --- a/manuals/bc/A.1.md +++ b/manuals/bc/A.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -419,9 +419,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -584,7 +584,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -933,8 +933,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1683,7 +1681,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/E.1 b/manuals/bc/E.1 index 6bacb680af67..d85db650606c 100644 --- a/manuals/bc/E.1 +++ b/manuals/bc/E.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,145 +44,147 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] 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]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -193,61 +193,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -255,270 +255,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -526,199 +524,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -728,152 +732,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -882,73 +886,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -960,27 +964,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -993,7 +997,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1001,230 +1005,259 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1232,65 +1265,65 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -1298,4 +1331,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/E.1.md b/manuals/bc/E.1.md index 3bec29912b77..ab432274fa52 100644 --- a/manuals/bc/E.1.md +++ b/manuals/bc/E.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -457,7 +457,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1075,7 +1075,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EH.1 b/manuals/bc/EH.1 index ed19e9769bd7..c9b196f7452a 100644 --- a/manuals/bc/EH.1 +++ b/manuals/bc/EH.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,142 +44,144 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .PP -\f[B]-g\f[R], \f[B]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -190,61 +190,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -252,270 +252,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -523,199 +521,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -725,152 +729,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -879,73 +883,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -957,27 +961,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -990,7 +994,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -998,281 +1002,310 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -1280,4 +1313,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EH.1.md b/manuals/bc/EH.1.md index 32d95f48fcee..32ef6e0d009f 100644 --- a/manuals/bc/EH.1.md +++ b/manuals/bc/EH.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -454,7 +454,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1059,7 +1059,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EHN.1 b/manuals/bc/EHN.1 index 39846195d4b3..0117a4cd0b68 100644 --- a/manuals/bc/EHN.1 +++ b/manuals/bc/EHN.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,142 +44,144 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .PP -\f[B]-g\f[R], \f[B]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -190,61 +190,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -252,270 +252,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -523,199 +521,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -725,152 +729,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -879,73 +883,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -957,27 +961,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -990,7 +994,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -998,274 +1002,303 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -1273,4 +1306,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EHN.1.md b/manuals/bc/EHN.1.md index 2eaf8145c90e..38b7cf78d76a 100644 --- a/manuals/bc/EHN.1.md +++ b/manuals/bc/EHN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -454,7 +454,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1051,7 +1051,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EHNP.1 b/manuals/bc/EHNP.1 index 231dc1d404c4..02b96492075d 100644 --- a/manuals/bc/EHNP.1 +++ b/manuals/bc/EHNP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,137 +44,139 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .PP -\f[B]-g\f[R], \f[B]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -185,61 +185,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -247,270 +247,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -518,199 +516,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -720,152 +724,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -874,73 +878,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -952,27 +956,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -985,7 +989,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -993,272 +997,301 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -1266,4 +1299,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EHNP.1.md b/manuals/bc/EHNP.1.md index 4138ffb98c5e..df608db015b4 100644 --- a/manuals/bc/EHNP.1.md +++ b/manuals/bc/EHNP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -450,7 +450,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1045,7 +1045,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EHP.1 b/manuals/bc/EHP.1 index 7dcc83b7bddd..cc2920f84403 100644 --- a/manuals/bc/EHP.1 +++ b/manuals/bc/EHP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,137 +44,139 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .PP -\f[B]-g\f[R], \f[B]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -185,61 +185,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -247,270 +247,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -518,199 +516,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -720,152 +724,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -874,73 +878,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -952,27 +956,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -985,7 +989,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -993,279 +997,308 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -1273,4 +1306,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EHP.1.md b/manuals/bc/EHP.1.md index c012f68fed43..0ce1f5209c21 100644 --- a/manuals/bc/EHP.1.md +++ b/manuals/bc/EHP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -450,7 +450,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1053,7 +1053,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EN.1 b/manuals/bc/EN.1 index d11c6f7742a1..d7f967d96cd5 100644 --- a/manuals/bc/EN.1 +++ b/manuals/bc/EN.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,145 +44,147 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] 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]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -193,61 +193,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -255,270 +255,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -526,199 +524,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -728,152 +732,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -882,73 +886,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -960,27 +964,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -993,7 +997,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1001,230 +1005,259 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1232,58 +1265,58 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -1291,4 +1324,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EN.1.md b/manuals/bc/EN.1.md index e7ba17a98401..55ca344ddeb2 100644 --- a/manuals/bc/EN.1.md +++ b/manuals/bc/EN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -457,7 +457,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1067,7 +1067,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/ENP.1 b/manuals/bc/ENP.1 index 0240b22b495a..736e26bd9acd 100644 --- a/manuals/bc/ENP.1 +++ b/manuals/bc/ENP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,140 +44,142 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] 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]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -188,61 +188,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -250,270 +250,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -521,199 +519,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -723,152 +727,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -877,73 +881,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -955,27 +959,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -988,7 +992,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -996,287 +1000,316 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -1284,4 +1317,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/ENP.1.md b/manuals/bc/ENP.1.md index 8e5b6fbdd27c..1eae3dee00d1 100644 --- a/manuals/bc/ENP.1.md +++ b/manuals/bc/ENP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -453,7 +453,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1061,7 +1061,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/EP.1 b/manuals/bc/EP.1 index 01f34378fd65..107342a54361 100644 --- a/manuals/bc/EP.1 +++ b/manuals/bc/EP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,140 +44,142 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] 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]\[en]global-stacks\f[R] +\f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] .IP .nf \f[C] -Turns the globals **ibase**, **obase**, and **scale** into 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: +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 - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ } -instead of like this: +instead\ of\ like\ this: - define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c - } +\ \ \ \ define\ void\ output(x,\ b)\ { +\ \ \ \ \ \ \ \ auto\ c +\ \ \ \ \ \ \ \ c=obase +\ \ \ \ \ \ \ \ obase=b +\ \ \ \ \ \ \ \ x +\ \ \ \ \ \ \ \ obase=c +\ \ \ \ } -This makes writing functions much easier. +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 +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: +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] +\ \ \ \ 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. +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\ 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. +If\ **\-s**,\ **\-w**,\ or\ any\ equivalents\ are\ used,\ this\ option\ is\ ignored. -This is a **non-portable extension**. -\f[R] +This\ is\ a\ **non\-portable\ extension**. +\f[] .fi .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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. +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the library, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -188,61 +188,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -250,270 +250,268 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] built\-in function. -The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R]. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Number 6 is a \f[B]non-portable extension\f[R]. +Number 6 is a \f[B]non\-portable extension\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .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] +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -521,199 +519,205 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.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] -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). +.B \f[B]=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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 -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -723,152 +727,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -877,73 +881,73 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .SH LIBRARY .PP -All of the functions below are available when the \f[B]-l\f[R] or -\f[B]\[en]mathlib\f[R] command-line flags are given. +All of the functions below are available when the \f[B]\-l\f[] or +\f[B]\-\-mathlib\f[] 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 -\f[B]s(x)\f[R] -Returns the sine of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Transcendental Functions .PP @@ -955,27 +959,27 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -988,7 +992,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -996,294 +1000,323 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator and the corresponding assignment operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -1291,4 +1324,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/EP.1.md b/manuals/bc/EP.1.md index a853961d683c..7e3d6aca7384 100644 --- a/manuals/bc/EP.1.md +++ b/manuals/bc/EP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -453,7 +453,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -1069,7 +1069,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/H.1 b/manuals/bc/H.1 index d6053feab4e8..48ccfb55b962 100644 --- a/manuals/bc/H.1 +++ b/manuals/bc/H.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,18 +44,18 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -65,40 +63,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -109,115 +107,118 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -226,61 +227,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -288,392 +289,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -681,264 +678,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -948,152 +951,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1102,23 +1105,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1126,528 +1129,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1659,55 +1679,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1720,7 +1740,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1728,289 +1748,320 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -2018,4 +2069,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/H.1.md b/manuals/bc/H.1.md index f764e47cc0f4..413032534554 100644 --- a/manuals/bc/H.1.md +++ b/manuals/bc/H.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -415,9 +415,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -580,7 +580,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -929,8 +929,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1666,7 +1664,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/HN.1 b/manuals/bc/HN.1 index 6a8dd876db65..9126c9209da5 100644 --- a/manuals/bc/HN.1 +++ b/manuals/bc/HN.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,18 +44,18 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -65,40 +63,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -109,115 +107,118 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -226,61 +227,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -288,392 +289,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -681,264 +678,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -948,152 +951,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1102,23 +1105,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1126,528 +1129,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1659,55 +1679,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1720,7 +1740,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1728,282 +1748,313 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -2011,4 +2062,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/HN.1.md b/manuals/bc/HN.1.md index 9cc71c3be057..c9ac146efbb2 100644 --- a/manuals/bc/HN.1.md +++ b/manuals/bc/HN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -415,9 +415,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -580,7 +580,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -929,8 +929,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1658,7 +1656,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/HNP.1 b/manuals/bc/HNP.1 index 30a8b00a5009..ad09513f0528 100644 --- a/manuals/bc/HNP.1 +++ b/manuals/bc/HNP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,18 +44,18 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -65,40 +63,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -109,110 +107,113 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -221,61 +222,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -283,392 +284,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -676,264 +673,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -943,152 +946,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1097,23 +1100,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1121,528 +1124,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1654,55 +1674,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1715,7 +1735,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1723,280 +1743,311 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -2004,4 +2055,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/HNP.1.md b/manuals/bc/HNP.1.md index 0425073d1c08..dc8c70ac09a9 100644 --- a/manuals/bc/HNP.1.md +++ b/manuals/bc/HNP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -411,9 +411,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -576,7 +576,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -925,8 +925,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1652,7 +1650,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/HP.1 b/manuals/bc/HP.1 index 2ece4e38cbd1..3ede3a2d5ca8 100644 --- a/manuals/bc/HP.1 +++ b/manuals/bc/HP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,18 +44,18 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .SH OPTIONS .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -65,40 +63,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -109,110 +107,113 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -221,61 +222,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -283,392 +284,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -676,264 +673,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -943,152 +946,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1097,23 +1100,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1121,528 +1124,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1654,55 +1674,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1715,7 +1735,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1723,287 +1743,318 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -2011,4 +2062,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/HP.1.md b/manuals/bc/HP.1.md index 482f1a482734..2c4053a302d0 100644 --- a/manuals/bc/HP.1.md +++ b/manuals/bc/HP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -411,9 +411,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -576,7 +576,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -925,8 +925,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1660,7 +1658,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/N.1 b/manuals/bc/N.1 index 9250b028635a..5c3e86157ba7 100644 --- a/manuals/bc/N.1 +++ b/manuals/bc/N.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,13 +44,13 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] bc(1), including (and especially) the GNU bc(1). It also has many extensions and extra features beyond other implementations. @@ -60,9 +58,9 @@ implementations. .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -70,40 +68,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -114,115 +112,118 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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). +\f[B]BC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT VARIABLES\f[] section). .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -231,61 +232,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -293,392 +294,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -686,264 +683,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -953,152 +956,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1107,23 +1110,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1131,528 +1134,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1664,55 +1684,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1725,7 +1745,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1733,238 +1753,269 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1972,58 +2023,58 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -2031,4 +2082,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/N.1.md b/manuals/bc/N.1.md index 63a5acf8ab47..9eabb2591eab 100644 --- a/manuals/bc/N.1.md +++ b/manuals/bc/N.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -419,9 +419,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -584,7 +584,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -933,8 +933,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1675,7 +1673,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/NP.1 b/manuals/bc/NP.1 index 89377821b179..8c2a2994a17f 100644 --- a/manuals/bc/NP.1 +++ b/manuals/bc/NP.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,13 +44,13 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] bc(1), including (and especially) the GNU bc(1). It also has many extensions and extra features beyond other implementations. @@ -60,9 +58,9 @@ implementations. .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -70,40 +68,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -114,110 +112,113 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -226,61 +227,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -288,392 +289,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -681,264 +678,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -948,152 +951,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1102,23 +1105,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1126,528 +1129,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1659,55 +1679,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1720,7 +1740,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1728,295 +1748,326 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .SH BUGS .PP None are known. @@ -2024,4 +2075,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/NP.1.md b/manuals/bc/NP.1.md index 60d6a7e59b37..be11fe236209 100644 --- a/manuals/bc/NP.1.md +++ b/manuals/bc/NP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -415,9 +415,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -580,7 +580,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -929,8 +929,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1669,7 +1667,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/bc/P.1 b/manuals/bc/P.1 index 688d6cb612b3..db807e440c28 100644 --- a/manuals/bc/P.1 +++ b/manuals/bc/P.1 @@ -25,20 +25,18 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "BC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "BC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH NAME .PP -bc - arbitrary-precision decimal arithmetic language and calculator +bc \- arbitrary\-precision arithmetic language and calculator .SH SYNOPSIS .PP -\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]\[en]global-stacks\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]mathlib\f[R]] [\f[B]\[en]no-prompt\f[R]] -[\f[B]\[en]quiet\f[R]] [\f[B]\[en]standard\f[R]] [\f[B]\[en]warn\f[R]] -[\f[B]\[en]version\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]bc\f[] [\f[B]\-ghilPqsvVw\f[]] [\f[B]\-\-global\-stacks\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-mathlib\f[]] +[\f[B]\-\-no\-prompt\f[]] [\f[B]\-\-quiet\f[]] [\f[B]\-\-standard\f[]] +[\f[B]\-\-warn\f[]] [\f[B]\-\-version\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP bc(1) is an interactive processor for a language first standardized in @@ -46,13 +44,13 @@ bc(1) is an interactive processor for a language first standardized in (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. +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]. +the command line and executes them before reading from \f[B]stdin\f[]. .PP -This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including +This bc(1) is a drop\-in replacement for \f[I]any\f[] bc(1), including (and especially) the GNU bc(1). It also has many extensions and extra features beyond other implementations. @@ -60,9 +58,9 @@ implementations. .PP The following are the options that bc(1) accepts. .TP -\f[B]-g\f[R], \f[B]\[en]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. +.B \f[B]\-g\f[], \f[B]\-\-global\-stacks\f[] +Turns the globals \f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], and +\f[B]seed\f[] into stacks. .RS .PP This has the effect that a copy of the current value of all four are @@ -70,40 +68,40 @@ 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: +Thus, a hypothetical function named \f[B]output(x,b)\f[] that simply +printed \f[B]x\f[] in base \f[B]b\f[] could be written like this: .IP .nf \f[C] -define void output(x, b) { - obase=b - x +define\ void\ output(x,\ b)\ { +\ \ \ \ obase=b +\ \ \ \ x } -\f[R] +\f[] .fi .PP instead of like this: .IP .nf \f[C] -define void output(x, b) { - auto c - c=obase - obase=b - x - obase=c +define\ void\ output(x,\ b)\ { +\ \ \ \ auto\ c +\ \ \ \ c=obase +\ \ \ \ obase=b +\ \ \ \ x +\ \ \ \ obase=c } -\f[R] +\f[] .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.) +(\f[B]Note\f[]: the function \f[B]output(x,b)\f[] exists in the extended +math library. +See the \f[B]LIBRARY\f[] 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] +\f[B]ibase\f[], \f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] globally, functions that are made to do so cannot work anymore. There are two possible use cases for that, and each has a solution. .PP @@ -114,110 +112,113 @@ Examples: .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] -\f[R] +alias\ d2o="bc\ \-e\ ibase=A\ \-e\ obase=8" +alias\ h2b="bc\ \-e\ ibase=G\ \-e\ obase=2" +\f[] .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. -.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 +Second, if the purpose of a function is to set \f[B]ibase\f[], +\f[B]obase\f[], \f[B]scale\f[], or \f[B]seed\f[] 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[], the value assigned to +\f[B]seed\f[] 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[] has been set. +.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[], it can use the following line: .IP .nf \f[C] -seed = seed -\f[R] +seed\ =\ seed +\f[] .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 +users could make sure to define \f[B]BC_ENV_ARGS\f[] and include this +option (see the \f[B]ENVIRONMENT VARIABLES\f[] section for more details). .PP -If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option +If \f[B]\-s\f[], \f[B]\-w\f[], or any equivalents are used, this option is ignored. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-l\f[R], \f[B]\[en]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 +.B \f[B]\-l\f[], \f[B]\-\-mathlib\f[] +Sets \f[B]scale\f[] (see the \f[B]SYNTAX\f[] section) to \f[B]20\f[] 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. +To learn what is in the libraries, see the \f[B]LIBRARY\f[] section. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-q\f[R], \f[B]\[en]quiet\f[R] +.B \f[B]\-q\f[], \f[B]\-\-quiet\f[] This option is for compatibility with the GNU -bc(1) (https://www.gnu.org/software/bc/); it is a no-op. +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]\[en]version\f[R] options are given. +\f[B]\-v\f[], \f[B]\-V\f[], or \f[B]\-\-version\f[] options are given. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-s\f[R], \f[B]\[en]standard\f[R] +.B \f[B]\-s\f[], \f[B]\-\-standard\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-w\f[R], \f[B]\[en]warn\f[R] -Like \f[B]-s\f[R] and \f[B]\[en]standard\f[R], except that warnings (and -not errors) are printed for non-standard extensions and execution +.B \f[B]\-w\f[], \f[B]\-\-warn\f[] +Like \f[B]\-s\f[] and \f[B]\-\-standard\f[], except that warnings (and +not errors) are printed for non\-standard extensions and execution continues normally. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -226,61 +227,61 @@ read in and evaluated first. .RS .PP 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]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP 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]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]bc +>&\-\f[], it will quit with an error. +This is done so that bc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other bc(1) implementations, this bc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]bc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .SH SYNTAX .PP -The syntax for bc(1) programs is mostly C-like, with some differences. +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) @@ -288,392 +289,388 @@ 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. +In the sections below, \f[B]E\f[] means expression, \f[B]S\f[] means +statement, and \f[B]I\f[] 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 (\f[B]I\f[]) start with a lowercase letter and can be +followed by any number (up to \f[B]BC_NAME_MAX\-1\f[]) of lowercase +letters (\f[B]a\-z\f[]), digits (\f[B]0\-9\f[]), and underscores +(\f[B]_\f[]). +The regex is \f[B][a\-z][a\-z0\-9_]*\f[]. Identifiers with more than one character (letter) are a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .PP -\f[B]ibase\f[R] is a global variable determining how to interpret +\f[B]ibase\f[] is a global variable determining how to interpret constant numbers. -It is the \[lq]input\[rq] 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]\[en]standard\f[R]) and \f[B]-w\f[R] -(\f[B]\[en]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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +If the \f[B]\-s\f[] (\f[B]\-\-standard\f[]) and \f[B]\-w\f[] +(\f[B]\-\-warn\f[]) flags were not given on the command line, the max +allowable value for \f[B]ibase\f[] is \f[B]36\f[]. +Otherwise, it is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in bc(1) +programs with the \f[B]maxibase()\f[] built\-in function. +.PP +\f[B]obase\f[] is a global variable determining how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]BC_BASE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxobase()\f[] 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 +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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] +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] 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). +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] is \f[B]BC_SCALE_MAX\f[] and +can be queried in bc(1) programs with the \f[B]maxscale()\f[] built\-in +function. +.PP +bc(1) has both \f[I]global\f[] variables and \f[I]local\f[] variables. +All \f[I]local\f[] variables are local to the function; they are +parameters or are introduced in the \f[B]auto\f[] list of a function +(see the \f[B]FUNCTIONS\f[] 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 +\f[B]auto\f[] list, it is assumed to be \f[I]global\f[]. +If a parent function has a \f[I]local\f[] variable version of a variable +that a child function considers \f[I]global\f[], the value of that +\f[I]global\f[] 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. +\f[I]global\f[] 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 +operator is an assignment operator \f[I]and\f[] 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]. +\f[B]last\f[]. +A single dot (\f[B].\f[]) may also be used as a synonym for +\f[B]last\f[]. +These are \f[B]non\-portable extensions\f[]. .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]. +Block comments are enclosed in \f[B]/*\f[] and \f[B]*/\f[]. .IP "2." 3 -Line comments go from \f[B]#\f[R] until, and not including, the next +Line comments go from \f[B]#\f[] until, and not including, the next newline. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Named Expressions .PP The following are named expressions in bc(1): .IP "1." 3 -Variables: \f[B]I\f[R] +Variables: \f[B]I\f[] .IP "2." 3 -Array Elements: \f[B]I[E]\f[R] +Array Elements: \f[B]I[E]\f[] .IP "3." 3 -\f[B]ibase\f[R] +\f[B]ibase\f[] .IP "4." 3 -\f[B]obase\f[R] +\f[B]obase\f[] .IP "5." 3 -\f[B]scale\f[R] +\f[B]scale\f[] .IP "6." 3 -\f[B]seed\f[R] +\f[B]seed\f[] .IP "7." 3 -\f[B]last\f[R] or a single dot (\f[B].\f[R]) +\f[B]last\f[] or a single dot (\f[B].\f[]) .PP -Numbers 6 and 7 are \f[B]non-portable extensions\f[R]. +Numbers 6 and 7 are \f[B]non\-portable extensions\f[]. .PP -The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random +The meaning of \f[B]seed\f[] 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. +The \f[I]scale\f[] and sign of the value may be significant. +.PP +If a previously used \f[B]seed\f[] value is assigned to \f[B]seed\f[] +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[] value was previously used. +.PP +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if \f[B]seed\f[] is queried again immediately. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will +\f[I]not\f[] produce unique sequences of pseudo\-random numbers. +The value of \f[B]seed\f[] will change after any use of the +\f[B]rand()\f[] and \f[B]irand(E)\f[] operands (see the +\f[I]Operands\f[] subsection below), except if the parameter passed to +\f[B]irand(E)\f[] is \f[B]0\f[], \f[B]1\f[], 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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .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 +This also applies to functions (see the \f[B]FUNCTIONS\f[] 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). +\f[B]increment\f[]/\f[B]decrement\f[] operators and as the left side of +\f[B]assignment\f[] operators (see the \f[I]Operators\f[] 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). +Numbers (see the \f[I]Numbers\f[] subsection below). .IP " 2." 4 -Array indices (\f[B]I[E]\f[R]). +Array indices (\f[B]I[E]\f[]). .IP " 3." 4 -\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence). +\f[B](E)\f[]: The value of \f[B]E\f[] (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. +\f[B]sqrt(E)\f[]: The square root of \f[B]E\f[]. +\f[B]E\f[] 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]. +\f[B]length(E)\f[]: The number of significant decimal digits in +\f[B]E\f[]. .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]. +\f[B]length(I[])\f[]: The number of elements in the array \f[B]I\f[]. +This is a \f[B]non\-portable extension\f[]. .IP " 7." 4 -\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R]. +\f[B]scale(E)\f[]: The \f[I]scale\f[] of \f[B]E\f[]. .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]. +\f[B]abs(E)\f[]: The absolute value of \f[B]E\f[]. +This is a \f[B]non\-portable extension\f[]. .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. +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a non\-\f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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 +\f[B]read()\f[]: Reads a line from \f[B]stdin\f[] and uses that as an expression. -The result of that expression is the result of the \f[B]read()\f[R] +The result of that expression is the result of the \f[B]read()\f[] operand. -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxibase()\f[]: The max allowable \f[B]ibase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxobase()\f[]: The max allowable \f[B]obase\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxscale()\f[]: The max allowable \f[B]scale\f[]. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]rand()\f[]: A pseudo\-random integer between \f[B]0\f[] (inclusive) +and \f[B]BC_RAND_MAX\f[] (inclusive). +Using this operand will change the value of \f[B]seed\f[]. +This is a \f[B]non\-portable extension\f[]. .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 -\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 +\f[B]irand(E)\f[]: A pseudo\-random integer between \f[B]0\f[] +(inclusive) and the value of \f[B]E\f[] (exclusive). +If \f[B]E\f[] is negative or is a non\-integer (\f[B]E\f[]\[aq]s +\f[I]scale\f[] is not \f[B]0\f[]), an error is raised, and bc(1) resets +(see the \f[B]RESET\f[] section) while \f[B]seed\f[] remains unchanged. +If \f[B]E\f[] is larger than \f[B]BC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]BC_RAND_MAX+1\f[], 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]. +Using this operand will change the value of \f[B]seed\f[], unless the +value of \f[B]E\f[] is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is returned, and \f[B]seed\f[] is \f[I]not\f[] +changed. +This is a \f[B]non\-portable extension\f[]. .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]. +\f[B]maxrand()\f[]: The max integer returned by \f[B]rand()\f[]. +This is a \f[B]non\-portable extension\f[]. .PP -The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are +The integers generated by \f[B]rand()\f[] and \f[B]irand(E)\f[] 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. +the pseudo\-random number generator. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with \f[B]rand()\f[] and \f[B]irand(E)\f[] are guaranteed to +\f[I]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[I]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. .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]). +\f[B]1\f[] period for a radix. +Numbers can have up to \f[B]BC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]Z\f[] alone always equals decimal \f[B]35\f[]. .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 +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e\-3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +Using scientific notation is an error or warning if the \f[B]\-s\f[] or +\f[B]\-w\f[], 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]. +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and bc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if bc(1) is given the number string +\f[B]10e\-4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .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 -\f[B]++\f[R] \f[B]\[en]\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] Type: Prefix and Postfix .RS .PP Associativity: None .PP -Description: \f[B]increment\f[R], \f[B]decrement\f[R] +Description: \f[B]increment\f[], \f[B]decrement\f[] .RE .TP -\f[B]-\f[R] \f[B]!\f[R] +.B \f[B]\-\f[] \f[B]!\f[] Type: Prefix .RS .PP Associativity: None .PP -Description: \f[B]negation\f[R], \f[B]boolean not\f[R] +Description: \f[B]negation\f[], \f[B]boolean not\f[] .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] Type: Postfix .RS .PP Associativity: None .PP -Description: \f[B]truncation\f[R] +Description: \f[B]truncation\f[] .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]set precision\f[R] +Description: \f[B]set precision\f[] .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]power\f[R] +Description: \f[B]power\f[] .RE .TP -\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R] +.B \f[B]*\f[] \f[B]/\f[] \f[B]%\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R] +Description: \f[B]multiply\f[], \f[B]divide\f[], \f[B]modulus\f[] .RE .TP -\f[B]+\f[R] \f[B]-\f[R] +.B \f[B]+\f[] \f[B]\-\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]add\f[R], \f[B]subtract\f[R] +Description: \f[B]add\f[], \f[B]subtract\f[] .RE .TP -\f[B]<<\f[R] \f[B]>>\f[R] +.B \f[B]<<\f[] \f[B]>>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]shift left\f[R], \f[B]shift right\f[R] +Description: \f[B]shift left\f[], \f[B]shift right\f[] .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] +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] Type: Binary .RS .PP Associativity: Right .PP -Description: \f[B]assignment\f[R] +Description: \f[B]assignment\f[] .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] +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]relational\f[R] +Description: \f[B]relational\f[] .RE .TP -\f[B]&&\f[R] +.B \f[B]&&\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean and\f[R] +Description: \f[B]boolean and\f[] .RE .TP -\f[B]||\f[R] +.B \f[B]||\f[] Type: Binary .RS .PP Associativity: Left .PP -Description: \f[B]boolean or\f[R] +Description: \f[B]boolean or\f[] .RE .PP The operators will be described in more detail below. .TP -\f[B]++\f[R] \f[B]\[en]\f[R] -The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R] +.B \f[B]++\f[] \f[B]\-\-\f[] +The prefix and postfix \f[B]increment\f[] and \f[B]decrement\f[] operators behave exactly like they would in C. -They require a named expression (see the \f[I]Named Expressions\f[R] +They require a named expression (see the \f[I]Named Expressions\f[] subsection) as an operand. .RS .PP @@ -681,264 +678,270 @@ 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 -to negate any expression with the value \f[B]0\f[R]. +.B \f[B]\-\f[] +The \f[B]negation\f[] operator returns \f[B]0\f[] if a user attempts to +negate any expression with the value \f[B]0\f[]. Otherwise, a copy of the expression with its sign flipped is returned. +.RS +.RE .TP -\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. +.B \f[B]!\f[] +The \f[B]boolean not\f[] operator returns \f[B]1\f[] if the expression +is \f[B]0\f[], or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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. +.B \f[B]$\f[] +The \f[B]truncation\f[] operator returns a copy of the given expression +with all of its \f[I]scale\f[] removed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\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 +.B \f[B]\@\f[] +The \f[B]set precision\f[] operator takes two expressions and returns a +copy of the first with its \f[I]scale\f[] 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 +the \f[I]scale\f[] 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. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] -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 +.B \f[B]^\f[] +The \f[B]power\f[] operator (not the \f[B]exclusive or\f[] 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 .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. +The second expression must be an integer (no \f[I]scale\f[]), 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, +.B \f[B]*\f[] +The \f[B]multiply\f[] 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 -\f[B]/\f[R] -The \f[B]divide\f[R] operator takes two expressions, divides them, and +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE +.TP +.B \f[B]/\f[] +The \f[B]divide\f[] 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]. +The \f[I]scale\f[] of the result shall be the value of \f[B]scale\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]%\f[R] -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]. +.B \f[B]%\f[] +The \f[B]modulus\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and evaluates them by 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[] and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .RS .PP -The second expression must be non-zero. +The second expression must be non\-zero. .RE .TP -\f[B]+\f[R] -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]. +.B \f[B]+\f[] +The \f[B]add\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the sum, with a \f[I]scale\f[] equal to the max +of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\f[B]-\f[R] -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]. +.B \f[B]\-\f[] +The \f[B]subtract\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns the difference, with a \f[I]scale\f[] equal to +the max of the \f[I]scale\f[]s of \f[B]a\f[] and \f[B]b\f[]. +.RS +.RE .TP -\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. +.B \f[B]<<\f[] +The \f[B]left shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the right. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]>>\f[R] -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. +.B \f[B]>>\f[] +The \f[B]right shift\f[] operator takes two expressions, \f[B]a\f[] and +\f[B]b\f[], and returns a copy of the value of \f[B]a\f[] with its +decimal point moved \f[B]b\f[] places to the left. .RS .PP -The second expression must be an integer (no \f[I]scale\f[R]) and -non-negative. +The second expression must be an integer (no \f[I]scale\f[]) and +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .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). +.B \f[B]=\f[] \f[B]<<=\f[] \f[B]>>=\f[] \f[B]+=\f[] \f[B]\-=\f[] \f[B]*=\f[] \f[B]/=\f[] \f[B]%=\f[] \f[B]^=\f[] \f[B]\@=\f[] +The \f[B]assignment\f[] operators take two expressions, \f[B]a\f[] and +\f[B]b\f[] where \f[B]a\f[] is a named expression (see the \f[I]Named +Expressions\f[] 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]. +For \f[B]=\f[], \f[B]b\f[] is copied and the result is assigned to +\f[B]a\f[]. +For all others, \f[B]a\f[] and \f[B]b\f[] are applied as operands to the +corresponding arithmetic operator and the result is assigned to +\f[B]a\f[]. .PP -The \f[B]assignment\f[R] operators that correspond to operators that are -extensions are themselves \f[B]non-portable extensions\f[R]. +The \f[B]assignment\f[] operators that correspond to operators that are +extensions are themselves \f[B]non\-portable extensions\f[]. .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]. +.B \f[B]==\f[] \f[B]<=\f[] \f[B]>=\f[] \f[B]!=\f[] \f[B]<\f[] \f[B]>\f[] +The \f[B]relational\f[] operators compare two expressions, \f[B]a\f[] +and \f[B]b\f[], and if the relation holds, according to C language +semantics, the result is \f[B]1\f[]. +Otherwise, it is \f[B]0\f[]. .RS .PP 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]. +\f[B]assignment\f[] operators, which means that \f[B]a=b>c\f[] is +interpreted as \f[B](a=b)>c\f[]. .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]. +This allowance is a \f[B]non\-portable extension\f[]. .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. +.B \f[B]&&\f[] +The \f[B]boolean and\f[] operator takes two expressions and returns +\f[B]1\f[] if both expressions are non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]||\f[R] -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. +.B \f[B]||\f[] +The \f[B]boolean or\f[] operator takes two expressions and returns +\f[B]1\f[] if one of the expressions is non\-zero, \f[B]0\f[] otherwise. .RS .PP -This is \f[I]not\f[R] a short-circuit operator. +This is \f[I]not\f[] a short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Statements .PP The following items are statements: .IP " 1." 4 -\f[B]E\f[R] +\f[B]E\f[] .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[] \f[B]S\f[] \f[B];\f[] ... +\f[B];\f[] \f[B]S\f[] \f[B]}\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]if\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] \f[B]else\f[] +\f[B]S\f[] .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] +\f[B]while\f[] \f[B](\f[] \f[B]E\f[] \f[B])\f[] \f[B]S\f[] .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] +\f[B]for\f[] \f[B](\f[] \f[B]E\f[] \f[B];\f[] \f[B]E\f[] \f[B];\f[] +\f[B]E\f[] \f[B])\f[] \f[B]S\f[] .IP " 7." 4 An empty statement .IP " 8." 4 -\f[B]break\f[R] +\f[B]break\f[] .IP " 9." 4 -\f[B]continue\f[R] +\f[B]continue\f[] .IP "10." 4 -\f[B]quit\f[R] +\f[B]quit\f[] .IP "11." 4 -\f[B]halt\f[R] +\f[B]halt\f[] .IP "12." 4 -\f[B]limits\f[R] +\f[B]limits\f[] .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[] \f[B]E\f[] \f[B],\f[] ... +\f[B],\f[] \f[B]E\f[] .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 +\f[B]I()\f[], \f[B]I(E)\f[], \f[B]I(E, E)\f[], and so on, where +\f[B]I\f[] is an identifier for a \f[B]void\f[] function (see the +\f[I]Void Functions\f[] subsection of the \f[B]FUNCTIONS\f[] section). +The \f[B]E\f[] argument(s) may also be arrays of the form \f[B]I[]\f[], +which will automatically be turned into array references (see the +\f[I]Array References\f[] subsection of the \f[B]FUNCTIONS\f[] 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[]. +.PP +Also, as a \f[B]non\-portable extension\f[], 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]. +constant \f[B]1\f[]. .PP -The \f[B]break\f[R] statement causes a loop to stop iterating and resume +The \f[B]break\f[] 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 +The \f[B]continue\f[] 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. +The \f[B]if\f[] \f[B]else\f[] 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). +The \f[B]quit\f[] 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 +The \f[B]halt\f[] statement causes bc(1) to quit, if it is executed. +(Unlike \f[B]quit\f[] if it is on a branch of an \f[B]if\f[] 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 +The \f[B]limits\f[] 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 +This is like the \f[B]quit\f[] 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[], and engineering notation is activated by assigning +\f[B]1\f[] to \f[B]obase\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .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 +run with either the \f[B]\-s\f[] or \f[B]\-w\f[] command\-line options (or equivalents). .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .SS Print Statement .PP -The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be -strings. +The "expressions" in a \f[B]print\f[] 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 @@ -948,152 +951,152 @@ below: tab(@); l l. T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T}@T{ -\f[B]\[rs]a\f[R] +\f[B]\\a\f[] T} T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T}@T{ -\f[B]\[rs]b\f[R] +\f[B]\\b\f[] T} T{ -\f[B]\[rs]\[rs]\f[R] +\f[B]\\\\\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]e\f[R] +\f[B]\\e\f[] T}@T{ -\f[B]\[rs]\f[R] +\f[B]\\\f[] T} T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T}@T{ -\f[B]\[rs]f\f[R] +\f[B]\\f\f[] T} T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T}@T{ -\f[B]\[rs]n\f[R] +\f[B]\\n\f[] T} T{ -\f[B]\[rs]q\f[R] +\f[B]\\q\f[] T}@T{ -\f[B]\[dq]\f[R] +\f[B]"\f[] T} T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T}@T{ -\f[B]\[rs]r\f[R] +\f[B]\\r\f[] T} T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T}@T{ -\f[B]\[rs]t\f[R] +\f[B]\\t\f[] T} .TE .PP Any other character following a backslash causes the backslash and -character to be printed as-is. +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. +Any non\-string expression in a print statement shall be assigned to +\f[B]last\f[], 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 +This means, for example, assuming that \f[B]i\f[] is equal to +\f[B]0\f[], in the expression .IP .nf \f[C] -a[i++] = i++ -\f[R] +a[i++]\ =\ i++ +\f[] .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. +the first (or 0th) element of \f[B]a\f[] is set to \f[B]1\f[], and +\f[B]i\f[] is equal to \f[B]2\f[] 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 +Thus, assuming \f[B]i\f[] is equal to \f[B]0\f[], this means that in the +expression .IP .nf \f[C] -x(i++, i++) -\f[R] +x(i++,\ i++) +\f[] .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. +the first argument passed to \f[B]x()\f[] is \f[B]0\f[], and the second +argument is \f[B]1\f[], while \f[B]i\f[] is equal to \f[B]2\f[] 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) +define\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return(E) } -\f[R] +\f[] .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. +Any \f[B]I\f[] in the parameter list or \f[B]auto\f[] list may be +replaced with \f[B]I[]\f[] to make a parameter or \f[B]auto\f[] var an +array, and any \f[B]I\f[] in the parameter list may be replaced with +\f[B]*I[]\f[] 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 +asterisk in the call; they must be called with just \f[B]I[]\f[] 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. +As a \f[B]non\-portable extension\f[], the opening brace of a +\f[B]define\f[] statement may appear on the next line. .PP -As a \f[B]non-portable extension\f[R], the return statement may also be +As a \f[B]non\-portable extension\f[], the return statement may also be in one of the following forms: .IP "1." 3 -\f[B]return\f[R] +\f[B]return\f[] .IP "2." 3 -\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R] +\f[B]return\f[] \f[B](\f[] \f[B])\f[] .IP "3." 3 -\f[B]return\f[R] \f[B]E\f[R] +\f[B]return\f[] \f[B]E\f[] .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 +The first two, or not specifying a \f[B]return\f[] statement, is +equivalent to \f[B]return (0)\f[], unless the function is a +\f[B]void\f[] function (see the \f[I]Void Functions\f[] subsection below). .SS Void Functions .PP -Functions can also be \f[B]void\f[R] functions, defined as follows: +Functions can also be \f[B]void\f[] functions, defined as follows: .IP .nf \f[C] -define void I(I,...,I){ - auto I,...,I - S;...;S - return +define\ void\ I(I,...,I){ +\ \ \ \ auto\ I,...,I +\ \ \ \ S;...;S +\ \ \ \ return } -\f[R] +\f[] .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 +Void functions can only use the first two \f[B]return\f[] 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 -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 -\f[B]define\f[R] keyword. +The word "void" is not treated as a keyword; it is still possible to +have variables, arrays, and functions named \f[B]void\f[]. +The word "void" is only treated specially right after the +\f[B]define\f[] keyword. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .SS Array References .PP For any array in the parameter list, if the array is declared in the @@ -1102,23 +1105,23 @@ form .nf \f[C] *I[] -\f[R] +\f[] .fi .PP -it is a \f[B]reference\f[R]. +it is a \f[B]reference\f[]. 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]. +This is a \f[B]non\-portable extension\f[]. .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]\[en]mathlib\f[R] command-line +library (see the \f[I]Extended Library\f[] subsection below), are +available when the \f[B]\-l\f[] or \f[B]\-\-mathlib\f[] 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 +when the \f[B]\-s\f[] option, the \f[B]\-w\f[] option, or equivalents are given. .SS Standard Library .PP @@ -1126,528 +1129,545 @@ 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. +.B \f[B]s(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]c(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]a(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]a(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l(x)\f[R] -Returns the natural logarithm of \f[B]x\f[R]. +.B \f[B]l(x)\f[] +Returns the natural logarithm of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]e(x)\f[R] -Returns the mathematical constant \f[B]e\f[R] raised to the power of -\f[B]x\f[R]. +.B \f[B]e(x)\f[] +Returns the mathematical constant \f[B]e\f[] raised to the power of +\f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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]. +.B \f[B]j(x, n)\f[] +Returns the bessel integer order \f[B]n\f[] (truncated) of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .SS Extended Library .PP -The extended library is \f[I]not\f[R] loaded when the -\f[B]-s\f[R]/\f[B]\[en]standard\f[R] or \f[B]-w\f[R]/\f[B]\[en]warn\f[R] +The extended library is \f[I]not\f[] loaded when the +\f[B]\-s\f[]/\f[B]\-\-standard\f[] or \f[B]\-w\f[]/\f[B]\-\-warn\f[] 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]. +The extended library is a \f[B]non\-portable extension\f[]. .TP -\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]. +.B \f[B]p(x, y)\f[] +Calculates \f[B]x\f[] to the power of \f[B]y\f[], even if \f[B]y\f[] is +not an integer, and returns the result to the current \f[B]scale\f[]. .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]. -.PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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 -the rounding mode round half away from -\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.B \f[B]r(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round half away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero). +.RS +.RE .TP -\f[B]ceil(x, p)\f[R] -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). +.B \f[B]ceil(x, p)\f[] +Returns \f[B]x\f[] rounded to \f[B]p\f[] decimal places according to the +rounding mode round away from +\f[B]0\f[] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero). +.RS +.RE .TP -\f[B]f(x)\f[R] -Returns the factorial of the truncated absolute value of \f[B]x\f[R]. +.B \f[B]f(x)\f[] +Returns the factorial of the truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]perm(n, k)\f[R] -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]. +.B \f[B]perm(n, k)\f[] +Returns the permutation of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]comb(n, k)\f[R] -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]. +.B \f[B]comb(n, k)\f[] +Returns the combination of the truncated absolute value of \f[B]n\f[] of +the truncated absolute value of \f[B]k\f[], if \f[B]k <= n\f[]. +If not, it returns \f[B]0\f[]. +.RS +.RE .TP -\f[B]l2(x)\f[R] -Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R]. +.B \f[B]l2(x)\f[] +Returns the logarithm base \f[B]2\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]l10(x)\f[R] -Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R]. +.B \f[B]l10(x)\f[] +Returns the logarithm base \f[B]10\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]log(x, b)\f[R] -Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R]. +.B \f[B]log(x, b)\f[] +Returns the logarithm base \f[B]b\f[] of \f[B]x\f[]. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]cbrt(x)\f[R] -Returns the cube root of \f[B]x\f[R]. +.B \f[B]cbrt(x)\f[] +Returns the cube root of \f[B]x\f[]. +.RS +.RE .TP -\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]. +.B \f[B]root(x, n)\f[] +Calculates the truncated value of \f[B]n\f[], \f[B]r\f[], and returns +the \f[B]r\f[]th root of \f[B]x\f[] to the current \f[B]scale\f[]. .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. +If \f[B]r\f[] is \f[B]0\f[] or negative, this raises an error and causes +bc(1) to reset (see the \f[B]RESET\f[] section). +It also raises an error and causes bc(1) to reset if \f[B]r\f[] is even +and \f[B]x\f[] is negative. .RE .TP -\f[B]pi(p)\f[R] -Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places. +.B \f[B]pi(p)\f[] +Returns \f[B]pi\f[] to \f[B]p\f[] decimal places. .RS .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]t(x)\f[R] -Returns the tangent of \f[B]x\f[R], which is assumed to be in radians. +.B \f[B]t(x)\f[] +Returns the tangent of \f[B]x\f[], 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]a2(y, x)\f[R] -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]a2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]sin(x)\f[] +Returns the sine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]s(x)\f[R]. +This is an alias of \f[B]s(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]cos(x)\f[] +Returns the cosine of \f[B]x\f[], which is assumed to be in radians. .RS .PP -This is an alias of \f[B]c(x)\f[R]. +This is an alias of \f[B]c(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] 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. +.B \f[B]tan(x)\f[] +Returns the tangent of \f[B]x\f[], 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). +If \f[B]x\f[] is equal to \f[B]1\f[] or \f[B]\-1\f[], this raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). .PP -This is an alias of \f[B]t(x)\f[R]. +This is an alias of \f[B]t(x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]atan(x)\f[R] -Returns the arctangent of \f[B]x\f[R], in radians. +.B \f[B]atan(x)\f[] +Returns the arctangent of \f[B]x\f[], in radians. .RS .PP -This is an alias of \f[B]a(x)\f[R]. +This is an alias of \f[B]a(x)\f[]. .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. -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 +Functions\f[] subsection below). +.RE +.TP +.B \f[B]atan2(y, x)\f[] +Returns the arctangent of \f[B]y/x\f[], in radians. +If both \f[B]y\f[] and \f[B]x\f[] are equal to \f[B]0\f[], it raises an +error and causes bc(1) to reset (see the \f[B]RESET\f[] section). +Otherwise, if \f[B]x\f[] is greater than \f[B]0\f[], it returns +\f[B]a(y/x)\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is greater than or +equal to \f[B]0\f[], it returns \f[B]a(y/x)+pi\f[]. +If \f[B]x\f[] is less than \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]a(y/x)\-pi\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is greater than +\f[B]0\f[], it returns \f[B]pi/2\f[]. +If \f[B]x\f[] is equal to \f[B]0\f[], and \f[B]y\f[] is less than +\f[B]0\f[], it returns \f[B]\-pi/2\f[]. +.RS +.PP +This function is the same as the \f[B]atan2()\f[] function in many programming languages. .PP -This is an alias of \f[B]a2(y, x)\f[R]. +This is an alias of \f[B]a2(y, x)\f[]. .PP This is a transcendental function (see the \f[I]Transcendental -Functions\f[R] subsection below). +Functions\f[] subsection below). .RE .TP -\f[B]r2d(x)\f[R] -Converts \f[B]x\f[R] from radians to degrees and returns the result. +.B \f[B]r2d(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]d2r(x)\f[R] -Converts \f[B]x\f[R] from degrees to radians and returns the result. +.B \f[B]d2r(x)\f[] +Converts \f[B]x\f[] 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). +Functions\f[] subsection below). .RE .TP -\f[B]frand(p)\f[R] -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. +.B \f[B]frand(p)\f[] +Generates a pseudo\-random number between \f[B]0\f[] (inclusive) and +\f[B]1\f[] (exclusive) with the number of decimal digits after the +decimal point equal to the truncated absolute value of \f[B]p\f[]. +If \f[B]p\f[] is not \f[B]0\f[], then calling this function will change +the value of \f[B]seed\f[]. +If \f[B]p\f[] is \f[B]0\f[], then \f[B]0\f[] is returned, and +\f[B]seed\f[] is \f[I]not\f[] changed. +.RS +.RE .TP -\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 +.B \f[B]ifrand(i, p)\f[] +Generates a pseudo\-random number that is between \f[B]0\f[] (inclusive) +and the truncated absolute value of \f[B]i\f[] (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. +absolute value of \f[B]p\f[]. +If the absolute value of \f[B]i\f[] is greater than or equal to +\f[B]2\f[], and \f[B]p\f[] is not \f[B]0\f[], then calling this function +will change the value of \f[B]seed\f[]; otherwise, \f[B]0\f[] is +returned and \f[B]seed\f[] is not changed. +.RS +.RE .TP -\f[B]srand(x)\f[R] -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]. +.B \f[B]srand(x)\f[] +Returns \f[B]x\f[] with its sign flipped with probability \f[B]0.5\f[]. +In other words, it randomizes the sign of \f[B]x\f[]. +.RS +.RE .TP -\f[B]brand()\f[R] -Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]). +.B \f[B]brand()\f[] +Returns a random boolean value (either \f[B]0\f[] or \f[B]1\f[]). +.RS +.RE .TP -\f[B]ubytes(x)\f[R] +.B \f[B]ubytes(x)\f[] Returns the numbers of unsigned integer bytes required to hold the -truncated absolute value of \f[B]x\f[R]. +truncated absolute value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]sbytes(x)\f[R] -Returns the numbers of signed, two\[cq]s-complement integer bytes -required to hold the truncated value of \f[B]x\f[R]. +.B \f[B]sbytes(x)\f[] +Returns the numbers of signed, two\[aq]s\-complement integer bytes +required to hold the truncated value of \f[B]x\f[]. +.RS +.RE .TP -\f[B]hex(x)\f[R] -Outputs the hexadecimal (base \f[B]16\f[R]) representation of -\f[B]x\f[R]. +.B \f[B]hex(x)\f[] +Outputs the hexadecimal (base \f[B]16\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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]. +.B \f[B]binary(x)\f[] +Outputs the binary (base \f[B]2\f[]) representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output(x, b)\f[R] -Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R]. +.B \f[B]output(x, b)\f[] +Outputs the base \f[B]b\f[] representation of \f[B]x\f[]. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]uint(x)\f[R] -Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as +.B \f[B]uint(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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] +If \f[B]x\f[] 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[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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 +.B \f[B]int(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] 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. .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). +If \f[B]x\f[] is not an integer, an error message is printed instead, +but bc(1) is not reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uintn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]n\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]intn(x, n)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]n\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]n\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]1\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]1\f[] byte, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int8(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]1\f[] 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 +If \f[B]x\f[] is not an integer or cannot fit into \f[B]1\f[] byte, an error message is printed instead, but bc(1) is not reset (see the -\f[B]RESET\f[R] section). +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]2\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int16(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]2\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]2\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]4\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int32(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]4\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]4\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]uint64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +an unsigned integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer, is negative, or cannot fit into +\f[B]8\f[] bytes, an error message is printed instead, but bc(1) is not +reset (see the \f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]int64(x)\f[] +Outputs the representation, in binary and hexadecimal, of \f[B]x\f[] as +a signed, two\[aq]s\-complement integer in \f[B]8\f[] 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). +If \f[B]x\f[] is not an integer or cannot fit into \f[B]8\f[] bytes, an +error message is printed instead, but bc(1) is not reset (see the +\f[B]RESET\f[] section). .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]hex_uint(x, n)\f[R] -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. +.B \f[B]hex_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in hexadecimal using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]binary_uint(x, n)\f[R] -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. +.B \f[B]binary_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in binary using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .TP -\f[B]output_uint(x, n)\f[R] -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. +.B \f[B]output_uint(x, n)\f[] +Outputs the representation of the truncated absolute value of \f[B]x\f[] +as an unsigned integer in the current \f[B]obase\f[] (see the +\f[B]SYNTAX\f[] section) using \f[B]n\f[] bytes. +Not all of the value will be output if \f[B]n\f[] is too small. .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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] 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. +.B \f[B]output_byte(x, i)\f[] +Outputs byte \f[B]i\f[] of the truncated absolute value of \f[B]x\f[], +where \f[B]0\f[] is the least significant byte and \f[B]number_of_bytes +\- 1\f[] 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). +This is a \f[B]void\f[] function (see the \f[I]Void Functions\f[] +subsection of the \f[B]FUNCTIONS\f[] section). .RE .SS Transcendental Functions .PP @@ -1659,55 +1679,55 @@ 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 +functions with the precision (\f[B]scale\f[]) 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. +If exact results are \f[I]absolutely\f[] required, users can double the +precision (\f[B]scale\f[]) and then truncate. .PP The transcendental functions in the standard math library are: .IP \[bu] 2 -\f[B]s(x)\f[R] +\f[B]s(x)\f[] .IP \[bu] 2 -\f[B]c(x)\f[R] +\f[B]c(x)\f[] .IP \[bu] 2 -\f[B]a(x)\f[R] +\f[B]a(x)\f[] .IP \[bu] 2 -\f[B]l(x)\f[R] +\f[B]l(x)\f[] .IP \[bu] 2 -\f[B]e(x)\f[R] +\f[B]e(x)\f[] .IP \[bu] 2 -\f[B]j(x, n)\f[R] +\f[B]j(x, n)\f[] .PP The transcendental functions in the extended math library are: .IP \[bu] 2 -\f[B]l2(x)\f[R] +\f[B]l2(x)\f[] .IP \[bu] 2 -\f[B]l10(x)\f[R] +\f[B]l10(x)\f[] .IP \[bu] 2 -\f[B]log(x, b)\f[R] +\f[B]log(x, b)\f[] .IP \[bu] 2 -\f[B]pi(p)\f[R] +\f[B]pi(p)\f[] .IP \[bu] 2 -\f[B]t(x)\f[R] +\f[B]t(x)\f[] .IP \[bu] 2 -\f[B]a2(y, x)\f[R] +\f[B]a2(y, x)\f[] .IP \[bu] 2 -\f[B]sin(x)\f[R] +\f[B]sin(x)\f[] .IP \[bu] 2 -\f[B]cos(x)\f[R] +\f[B]cos(x)\f[] .IP \[bu] 2 -\f[B]tan(x)\f[R] +\f[B]tan(x)\f[] .IP \[bu] 2 -\f[B]atan(x)\f[R] +\f[B]atan(x)\f[] .IP \[bu] 2 -\f[B]atan2(y, x)\f[R] +\f[B]atan2(y, x)\f[] .IP \[bu] 2 -\f[B]r2d(x)\f[R] +\f[B]r2d(x)\f[] .IP \[bu] 2 -\f[B]d2r(x)\f[R] +\f[B]d2r(x)\f[] .SH RESET .PP -When bc(1) encounters an error or a signal that it has a non-default +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 @@ -1720,7 +1740,7 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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 @@ -1728,302 +1748,333 @@ 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. +Most bc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]BC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]BC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]BC_BASE_DIGS\f[R]. +\f[B]BC_BASE_DIGS\f[]. .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. +The actual values of \f[B]BC_LONG_BIT\f[] and \f[B]BC_BASE_DIGS\f[] can +be queried with the \f[B]limits\f[] 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 +This integer type depends on the value of \f[B]BC_LONG_BIT\f[], 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 -\f[B]BC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]BC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]BC_BASE_DIGS\f[R] +.B \f[B]BC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_POW\f[R] +.B \f[B]BC_BASE_POW\f[] 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]. +\f[B]BC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]BC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]BC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]BC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]BC_LONG_BIT\f[R]. +Depends on \f[B]BC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]BC_BASE_MAX\f[R] +.B \f[B]BC_BASE_MAX\f[] The maximum output base. -Set at \f[B]BC_BASE_POW\f[R]. +Set at \f[B]BC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]BC_DIM_MAX\f[R] +.B \f[B]BC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +.B \f[B]BC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_STRING_MAX\f[R] +.B \f[B]BC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NAME_MAX\f[R] +.B \f[B]BC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]BC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_NUM_MAX\f[R] +.B \f[B]BC_NUM_MAX\f[] 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]. +Set at \f[B]BC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]BC_RAND_MAX\f[R] -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]. +.B \f[B]BC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]rand()\f[] operand. +Set at \f[B]2^BC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]BC_OVERFLOW_MAX\f[R]. +Set at \f[B]BC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .PP -The actual values can be queried with the \f[B]limits\f[R] statement. +The actual values can be queried with the \f[B]limits\f[] 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. +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 -\f[B]POSIXLY_CORRECT\f[R] +.B \f[B]POSIXLY_CORRECT\f[] If this variable exists (no matter the contents), bc(1) behaves as if -the \f[B]-s\f[R] option was given. +the \f[B]\-s\f[] option was given. +.RS +.RE .TP -\f[B]BC_ENV_ARGS\f[R] -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. +.B \f[B]BC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]BC_ENV_ARGS\f[] 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. .RS .PP -The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]BC_ENV_ARGS\f[] 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. +For example, the string \f[B]"/home/gavin/some bc file.bc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "bc" +file.bc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]BC_ENV_ARGS\f[] 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 -\f[B]BC_LINE_LENGTH\f[R] +.B \f[B]BC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), bc(1) will output lines to that length, including +the backslash (\f[B]\\\f[]). +The default line length is \f[B]70\f[]. +.RS +.RE .SH EXIT STATUS .PP bc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]<<\f[]), and +right shift (\f[B]>>\f[]) operators and their corresponding assignment +operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], 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, +\f[I]Named Expressions\f[] subsection of the \f[B]SYNTAX\f[] section), +giving an invalid \f[B]auto\f[] list, having a duplicate +\f[B]auto\f[]/function parameter, failing to find the end of a code +block, attempting to return a value from a \f[B]void\f[] 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. +when the option \f[B]\-s\f[] or any equivalents were given. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 -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. +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] 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[] function call as a value in an expression. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, bc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +bc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] 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]\[en]interactive\f[R] option can turn it on in other cases. +bc(1) has an interactive mode and a non\-interactive mode. +Interactive mode is turned on automatically when both \f[B]stdin\f[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, bc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If bc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when bc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +bc(1) supports interactive command\-line editing. +If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGES\f[]. .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) +bc(1) is compliant with the IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. -The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions +The flags \f[B]\-efghiqsvVw\f[], 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]. +numbers that use a period (\f[B].\f[]) as a radix point, regardless of +the value of \f[B]LC_NUMERIC\f[]. .PP This bc(1) supports error messages for different locales, and thus, it -supports \f[B]LC_MESSAGES\f[R]. +supports \f[B]LC_MESSAGES\f[]. .SH BUGS .PP None are known. @@ -2031,4 +2082,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHORS .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/bc/P.1.md b/manuals/bc/P.1.md index af712806cfc7..1058a91aa6d2 100644 --- a/manuals/bc/P.1.md +++ b/manuals/bc/P.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # NAME -bc - arbitrary-precision decimal arithmetic language and calculator +bc - arbitrary-precision arithmetic language and calculator # SYNOPSIS @@ -415,9 +415,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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. @@ -580,7 +580,7 @@ The operators will be described in more detail below. : 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. The second expression must be an integer (no *scale*), and if it is negative, the first value must be non-zero. @@ -929,8 +929,6 @@ The extended library is a **non-portable extension**. : 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). @@ -1677,7 +1675,7 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHORS -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html [2]: https://www.gnu.org/software/bc/ diff --git a/manuals/build.md b/manuals/build.md index 47fbabdfad7f..906551cc73ac 100644 --- a/manuals/build.md +++ b/manuals/build.md @@ -282,29 +282,6 @@ following forms: --option=arg ``` -### 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 To build `bc` only (no `dc`), use any one of the following commands for the diff --git a/manuals/dc.1.md.in b/manuals/dc.1.md.in index 5308b1c604a5..abb1c4aac773 100644 --- a/manuals/dc.1.md.in +++ b/manuals/dc.1.md.in @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -235,9 +235,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that {{ 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**. +**\<number\>e\<integer\>**. The power (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 @@ -355,8 +355,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1253,6 +1252,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/A.1 b/manuals/dc/A.1 index c993afb1fd4e..001fe5a1f2c5 100644 --- a/manuals/dc/A.1 +++ b/manuals/dc/A.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,167 +119,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -287,16 +287,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -304,25 +303,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -333,434 +334,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -768,18 +796,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -787,26 +815,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -818,154 +846,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -975,31 +1009,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1007,31 +1047,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1044,228 +1084,261 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1273,56 +1346,56 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1331,4 +1404,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/A.1.md b/manuals/dc/A.1.md index d48b2429aaa2..50c7c8f08c6b 100644 --- a/manuals/dc/A.1.md +++ b/manuals/dc/A.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -222,9 +222,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -339,8 +339,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1190,6 +1189,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/E.1 b/manuals/dc/E.1 index 1e04920d51fd..f5b1f194f206 100644 --- a/manuals/dc/E.1 +++ b/manuals/dc/E.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,113 +119,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -231,7 +232,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -239,25 +240,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -268,303 +271,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -572,18 +602,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -591,26 +621,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -622,154 +652,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -779,31 +815,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -811,31 +853,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -848,220 +890,251 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1069,56 +1142,56 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1127,4 +1200,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/E.1.md b/manuals/dc/E.1.md index 3ccf45a98ae3..bb2ab4b0366d 100644 --- a/manuals/dc/E.1.md +++ b/manuals/dc/E.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -289,8 +289,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1026,6 +1025,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EH.1 b/manuals/dc/EH.1 index 5ccc64ea725e..9c5cf7d14c92 100644 --- a/manuals/dc/EH.1 +++ b/manuals/dc/EH.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,113 +119,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -231,7 +232,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -239,25 +240,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -268,303 +271,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -572,18 +602,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -591,26 +621,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -622,154 +652,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -779,31 +815,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -811,31 +853,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -848,262 +890,293 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1112,4 +1185,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EH.1.md b/manuals/dc/EH.1.md index b59a5ef71a0c..e1a0540d1243 100644 --- a/manuals/dc/EH.1.md +++ b/manuals/dc/EH.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -289,8 +289,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1013,6 +1012,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EHN.1 b/manuals/dc/EHN.1 index bce6e577df6c..4d95b4a1ac96 100644 --- a/manuals/dc/EHN.1 +++ b/manuals/dc/EHN.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,113 +119,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -231,7 +232,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -239,25 +240,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -268,303 +271,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -572,18 +602,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -591,26 +621,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -622,154 +652,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -779,31 +815,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -811,31 +853,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -848,258 +890,289 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1108,4 +1181,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EHN.1.md b/manuals/dc/EHN.1.md index fd1a0251fd04..1fe5ab8cac09 100644 --- a/manuals/dc/EHN.1.md +++ b/manuals/dc/EHN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -289,8 +289,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1008,6 +1007,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EHNP.1 b/manuals/dc/EHNP.1 index 98cdfd150436..aceea91027ad 100644 --- a/manuals/dc/EHNP.1 +++ b/manuals/dc/EHNP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,113 +114,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -226,7 +227,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -234,25 +235,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -263,303 +266,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -567,18 +597,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -586,26 +616,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -617,154 +647,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -774,31 +810,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -806,31 +848,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -843,256 +885,287 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1101,4 +1174,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EHNP.1.md b/manuals/dc/EHNP.1.md index c1d7457770e8..97585bba14bb 100644 --- a/manuals/dc/EHNP.1.md +++ b/manuals/dc/EHNP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -286,8 +286,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1003,6 +1002,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EHP.1 b/manuals/dc/EHP.1 index 5f930f841aa4..70e45ae52363 100644 --- a/manuals/dc/EHP.1 +++ b/manuals/dc/EHP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,113 +114,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -226,7 +227,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -234,25 +235,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -263,303 +266,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -567,18 +597,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -586,26 +616,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -617,154 +647,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -774,31 +810,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -806,31 +848,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -843,260 +885,291 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1105,4 +1178,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EHP.1.md b/manuals/dc/EHP.1.md index 2df787cef087..d101695a1c89 100644 --- a/manuals/dc/EHP.1.md +++ b/manuals/dc/EHP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -286,8 +286,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1008,6 +1007,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EN.1 b/manuals/dc/EN.1 index 561a0f665cfc..4c57b0dd03e3 100644 --- a/manuals/dc/EN.1 +++ b/manuals/dc/EN.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,113 +119,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -231,7 +232,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -239,25 +240,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -268,303 +271,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -572,18 +602,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -591,26 +621,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -622,154 +652,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -779,31 +815,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -811,31 +853,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -848,220 +890,251 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1069,52 +1142,52 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1123,4 +1196,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EN.1.md b/manuals/dc/EN.1.md index 01c40a8e34dc..e1826daa4e18 100644 --- a/manuals/dc/EN.1.md +++ b/manuals/dc/EN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -289,8 +289,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1021,6 +1020,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/ENP.1 b/manuals/dc/ENP.1 index 77a94af08310..2e8e2341a739 100644 --- a/manuals/dc/ENP.1 +++ b/manuals/dc/ENP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,113 +114,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -226,7 +227,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -234,25 +235,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -263,303 +266,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -567,18 +597,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -586,26 +616,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -617,154 +647,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -774,31 +810,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -806,31 +848,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -843,271 +885,302 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1116,4 +1189,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/ENP.1.md b/manuals/dc/ENP.1.md index 9eb8696d1755..cc5eea424fb2 100644 --- a/manuals/dc/ENP.1.md +++ b/manuals/dc/ENP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -286,8 +286,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1016,6 +1015,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/EP.1 b/manuals/dc/EP.1 index 9a41956d67a5..f97f2a8ae98f 100644 --- a/manuals/dc/EP.1 +++ b/manuals/dc/EP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,113 +114,112 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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]. +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]2\f[]. 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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] 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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -226,7 +227,7 @@ The valid commands are listed below. .PP These commands are used for printing. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -234,25 +235,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -263,303 +266,330 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], and +\f[B]scale\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]2\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -567,18 +597,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -586,26 +616,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -617,154 +647,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -774,31 +810,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -806,31 +848,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -843,275 +885,306 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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. +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. +power (\f[B]^\f[]) operator. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1120,4 +1193,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/EP.1.md b/manuals/dc/EP.1.md index f9333fd29e19..cd58549b17a5 100644 --- a/manuals/dc/EP.1.md +++ b/manuals/dc/EP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -286,8 +286,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1021,6 +1020,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/H.1 b/manuals/dc/H.1 index 78f0f55603aa..44617c0b1a3c 100644 --- a/manuals/dc/H.1 +++ b/manuals/dc/H.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,167 +119,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -287,16 +287,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -304,25 +303,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -333,434 +334,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -768,18 +796,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -787,26 +815,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -818,154 +846,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -975,31 +1009,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1007,31 +1047,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1044,270 +1084,303 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1316,4 +1389,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/H.1.md b/manuals/dc/H.1.md index 6542f63d4fdc..327e27a0c893 100644 --- a/manuals/dc/H.1.md +++ b/manuals/dc/H.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -222,9 +222,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -339,8 +339,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1177,6 +1176,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/HN.1 b/manuals/dc/HN.1 index 2c8bde98b88a..8b032e82f1f9 100644 --- a/manuals/dc/HN.1 +++ b/manuals/dc/HN.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,167 +119,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -287,16 +287,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -304,25 +303,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -333,434 +334,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -768,18 +796,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -787,26 +815,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -818,154 +846,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -975,31 +1009,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1007,31 +1047,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1044,266 +1084,299 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1312,4 +1385,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/HN.1.md b/manuals/dc/HN.1.md index b81a98ffbf4f..f128840138a5 100644 --- a/manuals/dc/HN.1.md +++ b/manuals/dc/HN.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -222,9 +222,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -339,8 +339,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1172,6 +1171,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/HNP.1 b/manuals/dc/HNP.1 index a777eaa81074..f5152fa781d4 100644 --- a/manuals/dc/HNP.1 +++ b/manuals/dc/HNP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,167 +114,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -282,16 +282,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -299,25 +298,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -328,434 +329,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -763,18 +791,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -782,26 +810,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -813,154 +841,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -970,31 +1004,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1002,31 +1042,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1039,264 +1079,297 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1305,4 +1378,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/HNP.1.md b/manuals/dc/HNP.1.md index c4431fd7a4b2..fc71488f8b53 100644 --- a/manuals/dc/HNP.1.md +++ b/manuals/dc/HNP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -219,9 +219,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -336,8 +336,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1167,6 +1166,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/HP.1 b/manuals/dc/HP.1 index 872e6ef3e40b..eeae02949fc0 100644 --- a/manuals/dc/HP.1 +++ b/manuals/dc/HP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,167 +114,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -282,16 +282,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -299,25 +298,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -328,434 +329,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -763,18 +791,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -782,26 +810,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -813,154 +841,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -970,31 +1004,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1002,31 +1042,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1039,268 +1079,301 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1309,4 +1382,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/HP.1.md b/manuals/dc/HP.1.md index ffc61e93247b..88e0914d6266 100644 --- a/manuals/dc/HP.1.md +++ b/manuals/dc/HP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -219,9 +219,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -336,8 +336,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1172,6 +1171,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/N.1 b/manuals/dc/N.1 index 590d563faa50..a7ca5b5fec27 100644 --- a/manuals/dc/N.1 +++ b/manuals/dc/N.1 @@ -25,90 +25,92 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] 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[] 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]. +\f[B]DC_ENV_ARGS\f[]. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -117,167 +119,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -287,16 +287,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -304,25 +303,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -333,434 +334,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -768,18 +796,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -787,26 +815,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -818,154 +846,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -975,31 +1009,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1007,31 +1047,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1044,228 +1084,261 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] signals. .PP The prompt is enabled in TTY mode. @@ -1273,52 +1346,52 @@ The prompt is enabled in TTY mode. 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1327,4 +1400,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/N.1.md b/manuals/dc/N.1.md index ef94824c7a00..6e843649b37d 100644 --- a/manuals/dc/N.1.md +++ b/manuals/dc/N.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -222,9 +222,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -339,8 +339,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1185,6 +1184,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/NP.1 b/manuals/dc/NP.1 index 01c5f1e854f2..bfd1c0e59d4f 100644 --- a/manuals/dc/NP.1 +++ b/manuals/dc/NP.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,167 +114,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -282,16 +282,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -299,25 +298,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -328,434 +329,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -763,18 +791,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -782,26 +810,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -813,154 +841,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -970,31 +1004,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1002,31 +1042,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1039,279 +1079,312 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1320,4 +1393,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/NP.1.md b/manuals/dc/NP.1.md index e744a40c2474..b83d20a806bb 100644 --- a/manuals/dc/NP.1.md +++ b/manuals/dc/NP.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -219,9 +219,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -336,8 +336,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1180,6 +1179,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/manuals/dc/P.1 b/manuals/dc/P.1 index a39132aea914..6f5cd4cec1d3 100644 --- a/manuals/dc/P.1 +++ b/manuals/dc/P.1 @@ -25,85 +25,87 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.TH "DC" "1" "October 2020" "Gavin D. Howard" "General Commands Manual" +.TH "DC" "1" "July 2020" "Gavin D. Howard" "General Commands Manual" .SH Name .PP -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc \- arbitrary\-precision reverse\-Polish notation calculator .SH SYNOPSIS .PP -\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]] -[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]] -[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]] -[\f[B]-e\f[R] \f[I]expr\f[R]] -[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R] -\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...] -[\f[I]file\f[R]\&...] +\f[B]dc\f[] [\f[B]\-hiPvVx\f[]] [\f[B]\-\-version\f[]] +[\f[B]\-\-help\f[]] [\f[B]\-\-interactive\f[]] [\f[B]\-\-no\-prompt\f[]] +[\f[B]\-\-extended\-register\f[]] [\f[B]\-e\f[] \f[I]expr\f[]] +[\f[B]\-\-expression\f[]=\f[I]expr\f[]...] [\f[B]\-f\f[] +\f[I]file\f[]...] [\f[B]\-file\f[]=\f[I]file\f[]...] [\f[I]file\f[]...] .SH DESCRIPTION .PP -dc(1) is an arbitrary-precision calculator. +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]\[en]file\f[R] arguments), then dc(1) reads from -\f[B]stdin\f[R]. +If no files are given on the command\-line as extra arguments (i.e., not +as \f[B]\-f\f[] or \f[B]\-\-file\f[] arguments), then dc(1) reads from +\f[B]stdin\f[]. Otherwise, those files are processed, and dc(1) will then exit. .PP This is different from the dc(1) on OpenBSD and possibly other dc(1) -implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and -\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them +implementations, where \f[B]\-e\f[] (\f[B]\-\-expression\f[]) and +\f[B]\-f\f[] (\f[B]\-\-file\f[]) 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 +the environment variable \f[B]DC_ENV_ARGS\f[] (see the \f[B]ENVIRONMENT +VARIABLES\f[] 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]. +For example, if a user wants the \f[B]scale\f[] always set to +\f[B]10\f[], they can set \f[B]DC_ENV_ARGS\f[] to \f[B]\-e 10k\f[], and +this dc(1) will always start with a \f[B]scale\f[] of \f[B]10\f[]. .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]. +\f[B]\-e\f[] and \f[B]\-f\f[] arguments (and their equivalents), then +they can just simply add \f[B]\-e q\f[] as the last command\-line +argument or define the environment variable \f[B]DC_EXPR_EXIT\f[]. .SH OPTIONS .PP The following are the options that dc(1) accepts. .TP -\f[B]-h\f[R], \f[B]\[en]help\f[R] +.B \f[B]\-h\f[], \f[B]\-\-help\f[] Prints a usage message and quits. +.RS +.RE .TP -\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R] +.B \f[B]\-v\f[], \f[B]\-V\f[], \f[B]\-\-version\f[] Print the version information (copyright header) and exit. +.RS +.RE .TP -\f[B]-i\f[R], \f[B]\[en]interactive\f[R] +.B \f[B]\-i\f[], \f[B]\-\-interactive\f[] Forces interactive mode. -(See the \f[B]INTERACTIVE MODE\f[R] section.) +(See the \f[B]INTERACTIVE MODE\f[] section.) .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R] -This option is a no-op. +.B \f[B]\-P\f[], \f[B]\-\-no\-prompt\f[] +This option is a no\-op. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-x\f[R] \f[B]\[en]extended-register\f[R] +.B \f[B]\-x\f[] \f[B]\-\-extended\-register\f[] 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. +See the \f[I]Extended Register Mode\f[] subsection of the +\f[B]REGISTERS\f[] section for more information. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R] -Evaluates \f[I]expr\f[R]. +.B \f[B]\-e\f[] \f[I]expr\f[], \f[B]\-\-expression\f[]=\f[I]expr\f[] +Evaluates \f[I]expr\f[]. 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. @@ -112,167 +114,165 @@ read in and evaluated first. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R] -Reads in \f[I]file\f[R] and evaluates it, line by line, as though it -were read through \f[B]stdin\f[R]. +.B \f[B]\-f\f[] \f[I]file\f[], \f[B]\-\-file\f[]=\f[I]file\f[] +Reads in \f[I]file\f[] and evaluates it, line by line, as though it were +read through \f[B]stdin\f[]. If expressions are also given (see above), the expressions are evaluated in the order given. .RS .PP After processing all expressions and files, dc(1) will exit, unless -\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to -\f[B]-f\f[R] or \f[B]\[en]file\f[R]. -However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R], -\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that, -bc(1) will give a fatal error and exit. +\f[B]\-\f[] (\f[B]stdin\f[]) was given as an argument at least once to +\f[B]\-f\f[] or \f[B]\-\-file\f[]. +However, if any other \f[B]\-e\f[], \f[B]\-\-expression\f[], +\f[B]\-f\f[], or \f[B]\-\-file\f[] arguments are given after that, bc(1) +will give a fatal error and exit. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .PP -All long options are \f[B]non-portable extensions\f[R]. +All long options are \f[B]non\-portable extensions\f[]. .SH STDOUT .PP -Any non-error output is written to \f[B]stdout\f[R]. +Any non\-error output is written to \f[B]stdout\f[]. .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 +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stdout\f[], so if \f[B]stdout\f[] is closed, as in \f[B]dc +>&\-\f[], it will quit with an error. +This is done so that dc(1) can report problems when \f[B]stdout\f[] 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]. +redirect \f[B]stdout\f[] to \f[B]/dev/null\f[]. .SH STDERR .PP -Any error output is written to \f[B]stderr\f[R]. +Any error output is written to \f[B]stderr\f[]. .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. +\f[B]Note\f[]: Unlike other dc(1) implementations, this dc(1) will issue +a fatal error (see the \f[B]EXIT STATUS\f[] section) if it cannot write +to \f[B]stderr\f[], so if \f[B]stderr\f[] is closed, as in \f[B]dc +2>&\-\f[], 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. +\f[B]stderr\f[] 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]. +redirect \f[B]stderr\f[] to \f[B]/dev/null\f[]. .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] +\f[B]NUMBERS\f[] section) or a command (see the \f[B]COMMANDS\f[] 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 +\f[B]ibase\f[] is a register (see the \f[B]REGISTERS\f[] section) that determines how to interpret constant numbers. -It is the \[lq]input\[rq] 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 "input" base, or the number base used for interpreting input 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 +\f[B]ibase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]ibase\f[] is \f[B]16\f[]. +The min allowable value for \f[B]ibase\f[] is \f[B]2\f[]. +The max allowable value for \f[B]ibase\f[] can be queried in dc(1) +programs with the \f[B]T\f[] command. +.PP +\f[B]obase\f[] is a register (see the \f[B]REGISTERS\f[] section) that +determines how to output results. +It is the "output" base, or the number base used for outputting numbers. +\f[B]obase\f[] is initially \f[B]10\f[]. +The max allowable value for \f[B]obase\f[] is \f[B]DC_BASE_MAX\f[] and +can be queried with the \f[B]U\f[] command. +The min allowable value for \f[B]obase\f[] is \f[B]0\f[]. +If \f[B]obase\f[] is \f[B]0\f[], values are output in scientific +notation, and if \f[B]obase\f[] is \f[B]1\f[], 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]. +Outputting in scientific and engineering notations are +\f[B]non\-portable extensions\f[]. .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 +The \f[I]scale\f[] of an expression is the number of digits in the +result of the expression right of the decimal point, and \f[B]scale\f[] +is a register (see the \f[B]REGISTERS\f[] 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 -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 -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 -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[B]are\f[R] guaranteed to be reproducible with identical -\f[B]seed\f[R] values. -.PP -The pseudo-random number generator, \f[B]seed\f[R], and all associated -operations are \f[B]non-portable extensions\f[R]. +\f[B]scale\f[] is initially \f[B]0\f[]. +\f[B]scale\f[] cannot be negative. +The max allowable value for \f[B]scale\f[] can be queried in dc(1) +programs with the \f[B]V\f[] command. +.PP +\f[B]seed\f[] is a register containing the current seed for the +pseudo\-random number generator. +If the current value of \f[B]seed\f[] is queried and stored, then if it +is assigned to \f[B]seed\f[] 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[] was first queried. +.PP +Multiple values assigned to \f[B]seed\f[] can produce the same sequence +of pseudo\-random numbers. +Likewise, when a value is assigned to \f[B]seed\f[], it is not +guaranteed that querying \f[B]seed\f[] immediately after will return the +same value. +In addition, the value of \f[B]seed\f[] will change after any call to +the \f[B]\[aq]\f[] command or the \f[B]"\f[] command that does not get +receive a value of \f[B]0\f[] or \f[B]1\f[]. +The maximum integer returned by the \f[B]\[aq]\f[] command can be +queried with the \f[B]W\f[] command. +.PP +\f[B]Note\f[]: The values returned by the pseudo\-random number +generator with the \f[B]\[aq]\f[] and \f[B]"\f[] commands are guaranteed +to \f[B]NOT\f[] be cryptographically secure. +This is a consequence of using a seeded pseudo\-random number generator. +However, they \f[B]are\f[] guaranteed to be reproducible with identical +\f[B]seed\f[] values. +.PP +The pseudo\-random number generator, \f[B]seed\f[], and all associated +operations are \f[B]non\-portable extensions\f[]. .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]. +Comments go from \f[B]#\f[] until, and not including, the next newline. +This is a \f[B]non\-portable extension\f[]. .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]). +\f[B]F\f[], and at most \f[B]1\f[] period for a radix. +Numbers can have up to \f[B]DC_NUM_MAX\f[] digits. +Uppercase letters are equal to \f[B]9\f[] + their position in the +alphabet (i.e., \f[B]A\f[] equals \f[B]10\f[], or \f[B]9+1\f[]). 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]. +\f[B]ibase\f[], they are set to the value of the highest valid digit in +\f[B]ibase\f[]. .PP -Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that +Single\-character numbers (i.e., \f[B]A\f[] 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]. +\f[B]ibase\f[]. +This means that \f[B]A\f[] alone always equals decimal \f[B]10\f[] and +\f[B]F\f[] alone always equals decimal \f[B]15\f[]. .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]. +These have the form \f[B]<number>e<integer>\f[]. +The power (the portion after the \f[B]e\f[]) must be an integer. +An example is \f[B]1.89237e9\f[], which is equal to \f[B]1892370000\f[]. +Negative exponents are also allowed, so \f[B]4.2890e_3\f[] is equal to +\f[B]0.0042890\f[]. +.PP +\f[B]WARNING\f[]: Both the number and the exponent in scientific +notation are interpreted according to the current \f[B]ibase\f[], but +the number is still multiplied by \f[B]10^exponent\f[] regardless of the +current \f[B]ibase\f[]. +For example, if \f[B]ibase\f[] is \f[B]16\f[] and dc(1) is given the +number string \f[B]FFeA\f[], the resulting decimal number will be +\f[B]2550000000000\f[], and if dc(1) is given the number string +\f[B]10e_4\f[], the resulting decimal number will be \f[B]0.0016\f[]. +.PP +Accepting input as scientific notation is a \f[B]non\-portable +extension\f[]. .SH COMMANDS .PP The valid commands are listed below. @@ -282,16 +282,15 @@ 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]. +Scientific notation is activated by assigning \f[B]0\f[] to +\f[B]obase\f[] using \f[B]0o\f[], and engineering notation is activated +by assigning \f[B]1\f[] to \f[B]obase\f[] using \f[B]1o\f[]. +To deactivate them, just assign a different value to \f[B]obase\f[]. .PP Printing numbers in scientific notation and/or engineering notation is a -\f[B]non-portable extension\f[R]. +\f[B]non\-portable extension\f[]. .TP -\f[B]p\f[R] +.B \f[B]p\f[] Prints the value on top of the stack, whether number or string, and prints a newline after. .RS @@ -299,25 +298,27 @@ prints a newline after. This does not alter the stack. .RE .TP -\f[B]n\f[R] +.B \f[B]n\f[] Prints the value on top of the stack, whether number or string, and pops it off of the stack. +.RS +.RE .TP -\f[B]P\f[R] +.B \f[B]P\f[] Pops a value off the stack. .RS .PP 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 +result is printed as though \f[B]obase\f[] is \f[B]UCHAR_MAX+1\f[] and each digit is interpreted as an ASCII character, making it a byte stream. .PP If the value is a string, it is printed without a trailing newline. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]f\f[R] +.B \f[B]f\f[] Prints the entire contents of the stack, in order from newest to oldest, without altering anything. .RS @@ -328,434 +329,461 @@ Users should use this command when they get lost. .PP These are the commands used for arithmetic. .TP -\f[B]+\f[R] +.B \f[B]+\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]-\f[R] +.B \f[B]\-\f[] 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 +The \f[I]scale\f[] of the result is equal to the max \f[I]scale\f[] of both operands. +.RS +.RE .TP -\f[B]*\f[R] +.B \f[B]*\f[] 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. +If \f[B]a\f[] is the \f[I]scale\f[] of the first expression and +\f[B]b\f[] is the \f[I]scale\f[] of the second expression, the +\f[I]scale\f[] of the result is equal to +\f[B]min(a+b,max(scale,a,b))\f[] where \f[B]min()\f[] and \f[B]max()\f[] +return the obvious values. +.RS +.RE .TP -\f[B]/\f[R] +.B \f[B]/\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]%\f[R] +.B \f[B]%\f[] The top two values are popped off the stack, remaindered, and the result is pushed onto the stack. .RS .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]. +Remaindering is equivalent to 1) Computing \f[B]a/b\f[] to current +\f[B]scale\f[], and 2) Using the result of step 1 to calculate +\f[B]a\-(a/b)*b\f[] to \f[I]scale\f[] +\f[B]max(scale+scale(b),scale(a))\f[]. .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .RE .TP -\f[B]\[ti]\f[R] +.B \f[B]~\f[] 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. +This is equivalent to \f[B]x y / x y %\f[] except that \f[B]x\f[] and +\f[B]y\f[] are only evaluated once. .RS .PP -The first value popped off of the stack must be non-zero. +The first value popped off of the stack must be non\-zero. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[ha]\f[R] +.B \f[B]^\f[] 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 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. +non\-zero. .RE .TP -\f[B]v\f[R] +.B \f[B]v\f[] 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]. +The \f[I]scale\f[] of the result is equal to \f[B]scale\f[]. .RS .PP -The value popped off of the stack must be non-negative. +The value popped off of the stack must be non\-negative. .RE .TP -\f[B]_\f[R] -If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces +.B \f[B]_\f[] +If this command \f[I]immediately\f[] 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]. +This behavior without a number is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]b\f[R] +.B \f[B]b\f[] 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 .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]|\f[R] +.B \f[B]|\f[] 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 first value popped is used as the reduction modulus and must be an -integer and non-zero. +integer and non\-zero. The second value popped is used as the exponent and must be an integer -and non-negative. +and non\-negative. The third value popped is the base and must be an integer. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]$\f[R] +.B \f[B]$\f[] The top value is popped off the stack and copied, and the copy is truncated and pushed onto the stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[at]\f[R] +.B \f[B]\@\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]H\f[R] +.B \f[B]H\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]h\f[R] +.B \f[B]h\f[] 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. +non\-negative. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]G\f[R] +.B \f[B]G\f[] 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. +\f[B]1\f[] is pushed if they are equal, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]N\f[R] -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. +.B \f[B]N\f[] +The top value is popped off of the stack, and if it a \f[B]0\f[], a +\f[B]1\f[] is pushed; otherwise, a \f[B]0\f[] is pushed. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B](\f[R] +.B \f[B](\f[] 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. +\f[B]1\f[] is pushed if the first is less than the second, or \f[B]0\f[] +otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]{\f[R] +.B \f[B]{\f[] 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. +\f[B]1\f[] is pushed if the first is less than or equal to the second, +or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B])\f[R] +.B \f[B])\f[] 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. +\f[B]1\f[] is pushed if the first is greater than the second, or +\f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]}\f[R] +.B \f[B]}\f[] 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. +\f[B]1\f[] is pushed if the first is greater than or equal to the +second, or \f[B]0\f[] otherwise. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]M\f[R] +.B \f[B]M\f[] 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 +If they are both non\-zero, a \f[B]1\f[] is pushed onto the stack. +If either of them is zero, or both of them are, then a \f[B]0\f[] 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. +This is like the \f[B]&&\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]m\f[R] +.B \f[B]m\f[] 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 +If at least one of them is non\-zero, a \f[B]1\f[] is pushed onto the stack. -If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack. +If both of them are zero, then a \f[B]0\f[] 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. +This is like the \f[B]||\f[] operator in bc(1), and it is \f[I]not\f[] a +short\-circuit operator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE -.SS Pseudo-Random Number Generator +.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.) +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[] value that +controls the pseudo\-random number generator.) .PP -The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be +The pseudo\-random number generator is guaranteed to \f[B]NOT\f[] 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). +.B \f[B]\[aq]\f[] +Generates an integer between 0 and \f[B]DC_RAND_MAX\f[], inclusive (see +the \f[B]LIMITS\f[] section). .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]\[dq]\f[R] -Pops a value off of the stack, which is used as an \f[B]exclusive\f[R] +.B \f[B]"\f[] +Pops a value off of the stack, which is used as an \f[B]exclusive\f[] 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] +If the bound is negative or is a non\-integer, an error is raised, and +dc(1) resets (see the \f[B]RESET\f[] section) while \f[B]seed\f[] 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 +If the bound is larger than \f[B]DC_RAND_MAX\f[], the higher bound is +honored by generating several pseudo\-random integers, multiplying them +by appropriate powers of \f[B]DC_RAND_MAX+1\f[], 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. +Using this command will change the value of \f[B]seed\f[], unless the +operand is \f[B]0\f[] or \f[B]1\f[]. +In that case, \f[B]0\f[] is pushed onto the stack, and \f[B]seed\f[] is +\f[I]not\f[] changed. .RS .PP The generated integer is made as unbiased as possible, subject to the -limitations of the pseudo-random number generator. +limitations of the pseudo\-random number generator. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .SS Stack Control .PP These commands control the stack. .TP -\f[B]c\f[R] -Removes all items from (\[lq]clears\[rq]) the stack. +.B \f[B]c\f[] +Removes all items from ("clears") the stack. +.RS +.RE .TP -\f[B]d\f[R] -Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes -the copy onto the stack. +.B \f[B]d\f[] +Copies the item on top of the stack ("duplicates") and pushes the copy +onto the stack. +.RS +.RE .TP -\f[B]r\f[R] -Swaps (\[lq]reverses\[rq]) the two top items on the stack. +.B \f[B]r\f[] +Swaps ("reverses") the two top items on the stack. +.RS +.RE .TP -\f[B]R\f[R] -Pops (\[lq]removes\[rq]) the top value from the stack. +.B \f[B]R\f[] +Pops ("removes") the top value from the stack. +.RS +.RE .SS Register Control .PP -These commands control registers (see the \f[B]REGISTERS\f[R] section). +These commands control registers (see the \f[B]REGISTERS\f[] section). .TP -\f[B]s\f[R]\f[I]r\f[R] +.B \f[B]s\f[]\f[I]r\f[] Pops the value off the top of the stack and stores it into register -\f[I]r\f[R]. +\f[I]r\f[]. +.RS +.RE .TP -\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. -This does not alter the contents of \f[I]r\f[R]. +.B \f[B]l\f[]\f[I]r\f[] +Copies the value in register \f[I]r\f[] and pushes it onto the stack. +This does not alter the contents of \f[I]r\f[]. +.RS +.RE .TP -\f[B]S\f[R]\f[I]r\f[R] +.B \f[B]S\f[]\f[I]r\f[] Pops the value off the top of the (main) stack and pushes it onto the -stack of register \f[I]r\f[R]. +stack of register \f[I]r\f[]. The previous value of the register becomes inaccessible. +.RS +.RE .TP -\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 -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. +.B \f[B]L\f[]\f[I]r\f[] +Pops the value off the top of the stack for register \f[I]r\f[] and push +it onto the main stack. +The previous value in the stack for register \f[I]r\f[], if any, is now +accessible via the \f[B]l\f[]\f[I]r\f[] command. +.RS +.RE .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. +These commands control the values of \f[B]ibase\f[], \f[B]obase\f[], +\f[B]scale\f[], and \f[B]seed\f[]. +Also see the \f[B]SYNTAX\f[] section. .TP -\f[B]i\f[R] +.B \f[B]i\f[] 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], +\f[B]ibase\f[], which must be between \f[B]2\f[] and \f[B]16\f[], inclusive. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]o\f[R] +.B \f[B]o\f[] 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). +\f[B]obase\f[], which must be between \f[B]0\f[] and +\f[B]DC_BASE_MAX\f[], inclusive (see the \f[B]LIMITS\f[] section and the +\f[B]NUMBERS\f[] section). .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]k\f[R] +.B \f[B]k\f[] 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. +\f[B]scale\f[], which must be non\-negative. .RS .PP -If the value on top of the stack has any \f[I]scale\f[R], the -\f[I]scale\f[R] is ignored. +If the value on top of the stack has any \f[I]scale\f[], the +\f[I]scale\f[] is ignored. .RE .TP -\f[B]j\f[R] +.B \f[B]j\f[] 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 +\f[B]seed\f[]. +The meaning of \f[B]seed\f[] is dependent on the current pseudo\-random number generator but is guaranteed to not change except for new major versions. .RS .PP -The \f[I]scale\f[R] and sign of the value may be significant. +The \f[I]scale\f[] and sign of the value may be significant. .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] +If a previously used \f[B]seed\f[] 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[] value was previously used. .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. +The exact value assigned to \f[B]seed\f[] is not guaranteed to be +returned if the \f[B]J\f[] command is used. +However, if \f[B]seed\f[] \f[I]does\f[] return a different value, both +values, when assigned to \f[B]seed\f[], are guaranteed to produce the +same sequence of pseudo\-random numbers. +This means that certain values assigned to \f[B]seed\f[] will not +produce unique sequences of pseudo\-random numbers. .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]. +or \f[I]scale\f[] of the value that can be assigned to \f[B]seed\f[]. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]I\f[R] -Pushes the current value of \f[B]ibase\f[R] onto the main stack. +.B \f[B]I\f[] +Pushes the current value of \f[B]ibase\f[] onto the main stack. +.RS +.RE .TP -\f[B]O\f[R] -Pushes the current value of \f[B]obase\f[R] onto the main stack. +.B \f[B]O\f[] +Pushes the current value of \f[B]obase\f[] onto the main stack. +.RS +.RE .TP -\f[B]K\f[R] -Pushes the current value of \f[B]scale\f[R] onto the main stack. +.B \f[B]K\f[] +Pushes the current value of \f[B]scale\f[] onto the main stack. +.RS +.RE .TP -\f[B]J\f[R] -Pushes the current value of \f[B]seed\f[R] onto the main stack. +.B \f[B]J\f[] +Pushes the current value of \f[B]seed\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]T\f[R] -Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main +.B \f[B]T\f[] +Pushes the maximum allowable value of \f[B]ibase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]U\f[R] -Pushes the maximum allowable value of \f[B]obase\f[R] onto the main +.B \f[B]U\f[] +Pushes the maximum allowable value of \f[B]obase\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]V\f[R] -Pushes the maximum allowable value of \f[B]scale\f[R] onto the main +.B \f[B]V\f[] +Pushes the maximum allowable value of \f[B]scale\f[] onto the main stack. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]W\f[R] +.B \f[B]W\f[] Pushes the maximum (inclusive) integer that can be generated with the -\f[B]\[cq]\f[R] pseudo-random number generator command. +\f[B]\[aq]\f[] pseudo\-random number generator command. .RS .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .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. +\f[B]REGISTERS\f[] section) can hold both strings and numbers. dc(1) always knows whether the contents of a register are a string or a number. .PP @@ -763,18 +791,18 @@ 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 +For example, if the string \f[B][1pR]\f[] is executed as a macro, then +the code \f[B]1pR\f[] is executed, meaning that the \f[B]1\f[] 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 +.B \f[B][\f[]\f[I]characters\f[]\f[B]]\f[] +Makes a string containing \f[I]characters\f[] 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 +If there are brackets (\f[B][\f[] and \f[B]]\f[]) in the string, then they must be balanced. -Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R]) +Unbalanced brackets can be escaped using a backslash (\f[B]\\\f[]) character. .PP If there is a backslash character in the string, the character after it @@ -782,26 +810,26 @@ If there is a backslash character in the string, the character after it (first) backslash is not. .RE .TP -\f[B]a\f[R] +.B \f[B]a\f[] The value on top of the stack is popped. .RS .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 +The result mod \f[B]UCHAR_MAX+1\f[] is calculated. +If that result is \f[B]0\f[], push an empty string; otherwise, push a +one\-character string where the character is the result of the mod interpreted as an ASCII character. .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. +create the new string as a one\-character string. The new string is then pushed onto the stack. .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]x\f[R] +.B \f[B]x\f[] Pops a value off of the top of the stack. .RS .PP @@ -813,154 +841,160 @@ This behavior is the norm whenever a macro is executed, whether by this command or by the conditional execution commands below. .RE .TP -\f[B]>\f[R]\f[I]r\f[R] +.B \f[B]>\f[]\f[I]r\f[] 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. +register \f[I]r\f[] 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. +For example, \f[B]0 1>a\f[] will execute the contents of register +\f[B]a\f[], and \f[B]1 0>a\f[] will not. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!>\f[R]\f[I]r\f[R] +.B \f[B]!>\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!>\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]<\f[R]\f[I]r\f[R] +.B \f[B]<\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!<\f[R]\f[I]r\f[R] +.B \f[B]!<\f[]\f[I]r\f[] 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. +to), then the contents of register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!<\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]=\f[R]\f[I]r\f[R] +.B \f[B]=\f[]\f[I]r\f[] 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. +\f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]!=\f[R]\f[I]r\f[R] +.B \f[B]!=\f[]\f[I]r\f[] 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. +register \f[I]r\f[] are executed. .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). +error and reset (see the \f[B]RESET\f[] 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 +.B \f[B]!=\f[]\f[I]r\f[]\f[B]e\f[]\f[I]s\f[] +Like the above, but will execute register \f[I]s\f[] 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). +error and reset (see the \f[B]RESET\f[] section). .PP -This is a \f[B]non-portable extension\f[R]. +This is a \f[B]non\-portable extension\f[]. .RE .TP -\f[B]?\f[R] -Reads a line from the \f[B]stdin\f[R] and executes it. +.B \f[B]?\f[] +Reads a line from the \f[B]stdin\f[] and executes it. This is to allow macros to request input from users. +.RS +.RE .TP -\f[B]q\f[R] +.B \f[B]q\f[] 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. +.RS +.RE .TP -\f[B]Q\f[R] -Pops a value from the stack which must be non-negative and is used the +.B \f[B]Q\f[] +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. +.RS +.RE .SS Status .PP These commands query status of the stack or its top value. .TP -\f[B]Z\f[R] +.B \f[B]Z\f[] Pops a value off of the stack. .RS .PP @@ -970,31 +1004,37 @@ it has and pushes the result. If it is a string, pushes the number of characters the string has. .RE .TP -\f[B]X\f[R] +.B \f[B]X\f[] 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 +If it is a number, pushes the \f[I]scale\f[] of the value onto the stack. .PP -If it is a string, pushes \f[B]0\f[R]. +If it is a string, pushes \f[B]0\f[]. .RE .TP -\f[B]z\f[R] +.B \f[B]z\f[] Pushes the current stack depth (before execution of this command). +.RS +.RE .SS Arrays .PP These commands manipulate arrays. .TP -\f[B]:\f[R]\f[I]r\f[R] +.B \f[B]:\f[]\f[I]r\f[] 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. +The second value will be stored in the array \f[I]r\f[] (see the +\f[B]REGISTERS\f[] section), indexed by the first value. +.RS +.RE .TP -\f[B];\f[R]\f[I]r\f[R] +.B \f[B];\f[]\f[I]r\f[] Pops the value on top of the stack and uses it as an index into the -array \f[I]r\f[R]. +array \f[I]r\f[]. The selected value is then pushed onto the stack. +.RS +.RE .SH REGISTERS .PP Registers are names that can store strings, numbers, and arrays. @@ -1002,31 +1042,31 @@ Registers are names that can store strings, numbers, and arrays. .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 +All registers, when first referenced, have one value (\f[B]0\f[]) in their stack. .PP -In non-extended register mode, a register name is just the single +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 +The only exception is a newline (\f[B]\[aq]\\n\[aq]\f[]); 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]\[en]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]). +If extended register mode is enabled (\f[B]\-x\f[] or +\f[B]\-\-extended\-register\f[] command\-line arguments are given), then +normal single character registers are used \f[I]unless\f[] the character +immediately following a command that needs a register name is a space +(according to \f[B]isspace()\f[]) and not a newline +(\f[B]\[aq]\\n\[aq]\f[]). .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. +\f[B][a\-z][a\-z0\-9_]*\f[] (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 +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 @@ -1039,283 +1079,316 @@ Then the execution point is set so that any code waiting to execute 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; +(see the \f[B]EXIT STATUS\f[] 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. +Most dc(1) implementations use \f[B]char\f[] types to calculate the +value of \f[B]1\f[] 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 +It uses large integers to calculate more than \f[B]1\f[] 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. +If built in a environment where \f[B]DC_LONG_BIT\f[] (see the +\f[B]LIMITS\f[] section) is \f[B]64\f[], then each integer has +\f[B]9\f[] decimal digits. +If built in an environment where \f[B]DC_LONG_BIT\f[] is \f[B]32\f[] +then each integer has \f[B]4\f[] decimal digits. This value (the number of decimal digits per large integer) is called -\f[B]DC_BASE_DIGS\f[R]. +\f[B]DC_BASE_DIGS\f[]. .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 +This integer type depends on the value of \f[B]DC_LONG_BIT\f[], 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 -\f[B]DC_LONG_BIT\f[R] -The number of bits in the \f[B]long\f[R] type in the environment where +.B \f[B]DC_LONG_BIT\f[] +The number of bits in the \f[B]long\f[] 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). +integer (see the \f[B]PERFORMANCE\f[] section). +.RS +.RE .TP -\f[B]DC_BASE_DIGS\f[R] +.B \f[B]DC_BASE_DIGS\f[] 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]. +\f[B]PERFORMANCE\f[] section). +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_POW\f[R] +.B \f[B]DC_BASE_POW\f[] 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]. +\f[B]DC_BASE_DIGS\f[]) plus \f[B]1\f[]. +Depends on \f[B]DC_BASE_DIGS\f[]. +.RS +.RE .TP -\f[B]DC_OVERFLOW_MAX\f[R] -The max number that the overflow type (see the \f[B]PERFORMANCE\f[R] +.B \f[B]DC_OVERFLOW_MAX\f[] +The max number that the overflow type (see the \f[B]PERFORMANCE\f[] section) can hold. -Depends on \f[B]DC_LONG_BIT\f[R]. +Depends on \f[B]DC_LONG_BIT\f[]. +.RS +.RE .TP -\f[B]DC_BASE_MAX\f[R] +.B \f[B]DC_BASE_MAX\f[] The maximum output base. -Set at \f[B]DC_BASE_POW\f[R]. +Set at \f[B]DC_BASE_POW\f[]. +.RS +.RE .TP -\f[B]DC_DIM_MAX\f[R] +.B \f[B]DC_DIM_MAX\f[] The maximum size of arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_SCALE_MAX\f[R] -The maximum \f[B]scale\f[R]. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +.B \f[B]DC_SCALE_MAX\f[] +The maximum \f[B]scale\f[]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_STRING_MAX\f[R] +.B \f[B]DC_STRING_MAX\f[] The maximum length of strings. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NAME_MAX\f[R] +.B \f[B]DC_NAME_MAX\f[] The maximum length of identifiers. -Set at \f[B]DC_OVERFLOW_MAX-1\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_NUM_MAX\f[R] +.B \f[B]DC_NUM_MAX\f[] 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]. +Set at \f[B]DC_OVERFLOW_MAX\-1\f[]. +.RS +.RE .TP -\f[B]DC_RAND_MAX\f[R] -The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command, +.B \f[B]DC_RAND_MAX\f[] +The maximum integer (inclusive) returned by the \f[B]\[aq]\f[] command, if dc(1). -Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R]. +Set at \f[B]2^DC_LONG_BIT\-1\f[]. +.RS +.RE .TP -Exponent +.B Exponent The maximum allowable exponent (positive or negative). -Set at \f[B]DC_OVERFLOW_MAX\f[R]. +Set at \f[B]DC_OVERFLOW_MAX\f[]. +.RS +.RE .TP -Number of vars +.B Number of vars The maximum number of vars/arrays. -Set at \f[B]SIZE_MAX-1\f[R]. +Set at \f[B]SIZE_MAX\-1\f[]. +.RS +.RE .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. +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 -\f[B]DC_ENV_ARGS\f[R] -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. +.B \f[B]DC_ENV_ARGS\f[] +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 -files to be used at every invocation. +\f[B]DC_ENV_ARGS\f[] 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 \f[B]-e\f[R] option to set -\f[B]scale\f[R] to a value other than \f[B]0\f[R]. +Another use would be to use the \f[B]\-e\f[] option to set +\f[B]scale\f[] to a value other than \f[B]0\f[]. .RS .PP -The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted +The code that parses \f[B]DC_ENV_ARGS\f[] 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 `bc' file.bc\[dq]\f[R], and vice versa if you have a -file with double quotes. +For example, the string \f[B]"/home/gavin/some dc file.dc"\f[] will be +correctly parsed, but the string \f[B]"/home/gavin/some "dc" +file.dc"\f[] will include the backslashes. +.PP +The quote parsing will handle either kind of quotes, \f[B]\[aq]\f[] or +\f[B]"\f[]. +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]"some +\[aq]bc\[aq] file.bc"\f[], 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. +\f[B]DC_ENV_ARGS\f[] 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 -\f[B]DC_LINE_LENGTH\f[R] +.B \f[B]DC_LINE_LENGTH\f[] 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]. +greater than \f[B]1\f[] and is less than \f[B]UINT16_MAX\f[] +(\f[B]2^16\-1\f[]), dc(1) will output lines to that length, including +the backslash newline combo. +The default line length is \f[B]70\f[]. +.RS +.RE .TP -\f[B]DC_EXPR_EXIT\f[R] +.B \f[B]DC_EXPR_EXIT\f[] 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 +\f[B]\-e\f[] and/or \f[B]\-f\f[] command\-line options (and any equivalents). +.RS +.RE .SH EXIT STATUS .PP dc(1) returns the following exit statuses: .TP -\f[B]0\f[R] +.B \f[B]0\f[] No error. +.RS +.RE .TP -\f[B]1\f[R] +.B \f[B]1\f[] A math error occurred. -This follows standard practice of using \f[B]1\f[R] for expected errors, +This follows standard practice of using \f[B]1\f[] 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 +Math errors include divide by \f[B]0\f[], 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 +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 +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. +power (\f[B]^\f[]), places (\f[B]\@\f[]), left shift (\f[B]H\f[]), and +right shift (\f[B]h\f[]) operators. .RE .TP -\f[B]2\f[R] +.B \f[B]2\f[] A parse error occurred. .RS .PP -Parse errors include unexpected \f[B]EOF\f[R], using an invalid +Parse errors include unexpected \f[B]EOF\f[], using an invalid character, failing to find the end of a string or comment, and using a token where it is invalid. .RE .TP -\f[B]3\f[R] +.B \f[B]3\f[] 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 +Runtime errors include assigning an invalid number to \f[B]ibase\f[], +\f[B]obase\f[], or \f[B]scale\f[]; give a bad expression to a +\f[B]read()\f[] call, calling \f[B]read()\f[] inside of a +\f[B]read()\f[] call, type errors, and attempting an operation when the stack has too few elements. .RE .TP -\f[B]4\f[R] +.B \f[B]4\f[] 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. +directory as a file, and giving invalid command\-line options. .RE .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. +The exit status \f[B]4\f[] is special; when a fatal error occurs, dc(1) +always exits and returns \f[B]4\f[], 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. +interactive mode (see the \f[B]INTERACTIVE MODE\f[] section), since +dc(1) resets its state (see the \f[B]RESET\f[] section) and accepts more +input when one of those errors occurs in interactive mode. This is also the case when interactive mode is forced by the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .PP These exit statuses allow dc(1) to be used in shell scripting with error checking, and its normal behavior can be forced by using the -\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option. +\f[B]\-i\f[] flag or \f[B]\-\-interactive\f[] option. .SH INTERACTIVE MODE .PP -Like bc(1), dc(1) has an interactive mode and a non-interactive mode. -Interactive mode is turned on automatically when both \f[B]stdin\f[R] -and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag -and \f[B]\[en]interactive\f[R] option can turn it on in other cases. +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[] and +\f[B]stdout\f[] are hooked to a terminal, but the \f[B]\-i\f[] flag and +\f[B]\-\-interactive\f[] 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. +\f[B]RESET\f[] section), and in normal execution, flushes +\f[B]stdout\f[] 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] +If \f[B]stdin\f[], \f[B]stdout\f[], and \f[B]stderr\f[] are all +connected to a TTY, dc(1) turns on "TTY mode." .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] +LINE HISTORY\f[] section). +It is also required to enable special handling for \f[B]SIGINT\f[] 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. +and interactive mode requires only \f[B]stdin\f[] and \f[B]stdout\f[] 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 +Sending a \f[B]SIGINT\f[] 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). +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] section), it will +reset (see the \f[B]RESET\f[] section). Otherwise, it will clean up and exit. .PP -Note that \[lq]current input\[rq] can mean one of two things. -If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will +Note that "current input" can mean one of two things. +If dc(1) is processing input from \f[B]stdin\f[] 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. +or ask for input from \f[B]stdin\f[] 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 means that if a \f[B]SIGINT\f[] 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. +\f[B]SIGTERM\f[] and \f[B]SIGQUIT\f[] 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[]; in that case, when dc(1) is in TTY +mode, a \f[B]SIGHUP\f[] 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 +dc(1) supports interactive command\-line editing. +If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[] 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. +\f[B]Note\f[]: 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]. +locales and thus, supports \f[B]LC_MESSAGS\f[]. .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) +bc(1) IEEE Std 1003.1\-2017 +(“POSIX.1\-2017”) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html) specification. .SH BUGS .PP @@ -1324,4 +1397,4 @@ Report bugs at https://git.yzena.com/gavin/bc. .SH AUTHOR .PP Gavin D. -Howard <gavin@yzena.com> and contributors. +Howard <yzena.tech@gmail.com> and contributors. diff --git a/manuals/dc/P.1.md b/manuals/dc/P.1.md index 65771f6c73e1..41aad658bb3d 100644 --- a/manuals/dc/P.1.md +++ b/manuals/dc/P.1.md @@ -30,7 +30,7 @@ POSSIBILITY OF SUCH DAMAGE. # Name -dc - arbitrary-precision decimal reverse-Polish notation calculator +dc - arbitrary-precision reverse-Polish notation calculator # SYNOPSIS @@ -219,9 +219,9 @@ if they were valid digits, regardless of the value of **ibase**. This means that **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**. +**\<number\>e\<integer\>**. The power (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 @@ -336,8 +336,7 @@ These are the commands used for arithmetic. **\^** : 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**. + power of the first, and the result is pushed onto the stack. 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 @@ -1185,6 +1184,6 @@ None are known. Report bugs at https://git.yzena.com/gavin/bc. # AUTHOR -Gavin D. Howard <gavin@yzena.com> and contributors. +Gavin D. Howard <yzena.tech@gmail.com> and contributors. [1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html diff --git a/release.sh b/release.sh index bd9c33e55da6..d6cc74b43118 100755 --- a/release.sh +++ b/release.sh @@ -263,35 +263,6 @@ runtestseries() { 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" @@ -355,12 +326,6 @@ debug() { 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() { @@ -372,8 +337,6 @@ release() { shift runtests "$release" "$_release_CC" "-O3" "$_release_run_tests" - - runlibtests "$release" "$_release_CC" "-O3" "$_release_run_tests" } reldebug() { @@ -390,13 +353,6 @@ reldebug() { 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() { @@ -408,8 +364,6 @@ minsize() { shift runtests "$release" "$_minsize_CC" "-Os" "$_minsize_run_tests" - - runlibtests "$release" "$_minsize_CC" "-Os" "$_minsize_run_tests" } build_set() { diff --git a/src/args.c b/src/args.c index 4c9ad3b95549..029237627786 100644 --- a/src/args.c +++ b/src/args.c @@ -41,8 +41,10 @@ #include <unistd.h> +#include <status.h> #include <vector.h> #include <read.h> +#include <vm.h> #include <args.h> #include <opt.h> @@ -107,7 +109,7 @@ void bc_args(int argc, char *argv[]) { case 'e': { if (vm.no_exit_exprs) - bc_vm_verr(BC_ERR_FATAL_OPTION, "-e (--expression)"); + bc_vm_verr(BC_ERROR_FATAL_OPTION, "-e (--expression)"); bc_args_exprs(opts.optarg); break; } @@ -117,7 +119,7 @@ void bc_args(int argc, char *argv[]) { 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_vm_verr(BC_ERROR_FATAL_OPTION, "-f (--file)"); bc_args_file(opts.optarg); } break; diff --git a/src/data.c b/src/data.c index a3cf4dbda293..039c83e1cac1 100644 --- a/src/data.c +++ b/src/data.c @@ -43,8 +43,6 @@ #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); @@ -666,8 +664,11 @@ const char* bc_inst_names[] = { }; #endif // BC_DEBUG_CODE -const char bc_parse_zero[2] = "0"; -const char bc_parse_one[2] = "1"; +#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_ENABLED const BcLexKeyword bc_lex_kws[] = { @@ -711,6 +712,8 @@ const BcLexKeyword bc_lex_kws[] = { const size_t bc_lex_kws_len = sizeof(bc_lex_kws) / sizeof(BcLexKeyword); +const char* const bc_parse_const1 = "1"; + // 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[] = { @@ -934,26 +937,11 @@ const uchar dc_parse_insts[] = { }; #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, + 18U }; #else // BC_LONG_BIT >= 64 const BcDig bc_num_bigdigMax[] = { @@ -961,17 +949,12 @@ const BcDig bc_num_bigdigMax[] = { 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_parse_zero[] = "0"; +const char bc_parse_one[] = "1"; const char bc_num_hex_digits[] = "0123456789ABCDEF"; @@ -990,8 +973,6 @@ const BcBigDig bc_num_pow10[BC_BASE_DIGS + 1] = { #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 @@ -1000,7 +981,7 @@ const BcNumBinaryOp bc_program_ops[] = { }; const BcNumBinaryOpReq bc_program_opReqs[] = { - bc_num_powReq, bc_num_mulReq, bc_num_divReq, bc_num_divReq, + bc_num_powReq, bc_num_mulReq, bc_num_mulReq, bc_num_mulReq, bc_num_addReq, bc_num_addReq, #if BC_ENABLE_EXTRA_MATH bc_num_placesReq, bc_num_placesReq, bc_num_placesReq, @@ -1021,5 +1002,3 @@ 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/src/file.c b/src/file.c index 1d4d390f89a4..01997399f452 100644 --- a/src/file.c +++ b/src/file.c @@ -41,8 +41,8 @@ #include <file.h> #include <vm.h> -static void bc_file_ultoa(unsigned long long val, char buf[BC_FILE_ULL_LENGTH]) -{ +void bc_file_ultoa(unsigned long long val, char buf[BC_FILE_ULL_LENGTH]) { + char buf2[BC_FILE_ULL_LENGTH]; size_t i, len; @@ -105,7 +105,7 @@ void bc_file_flush(BcFile *restrict f) { vm.status = (sig_atomic_t) s; BC_VM_JMP; } - else bc_vm_err(BC_ERR_FATAL_IO_ERR); + else bc_vm_err(BC_ERROR_FATAL_IO_ERR); } } diff --git a/src/lang.c b/src/lang.c index bc34e7c269f8..bd287c75ee78 100644 --- a/src/lang.c +++ b/src/lang.c @@ -77,7 +77,7 @@ void bc_func_insert(BcFunc *f, BcProgram *p, char *name, BcLoc *id = bc_vec_item(&f->autos, i); if (BC_ERR(idx == id->loc && type == (BcType) id->idx)) { const char *array = type == BC_TYPE_ARRAY ? "[]" : ""; - bc_vm_error(BC_ERR_PARSE_DUP_LOCAL, line, name, array); + bc_vm_error(BC_ERROR_PARSE_DUP_LOCAL, line, name, array); } } diff --git a/src/lex.c b/src/lex.c index d6f09f995a6a..2b705c8bc71b 100644 --- a/src/lex.c +++ b/src/lex.c @@ -38,13 +38,14 @@ #include <stdbool.h> #include <string.h> +#include <status.h> #include <lex.h> #include <vm.h> #include <bc.h> void bc_lex_invalidChar(BcLex *l, char c) { l->t = BC_LEX_INVALID; - bc_lex_verr(l, BC_ERR_PARSE_CHAR, c); + bc_lex_verr(l, BC_ERROR_PARSE_CHAR, c); } void bc_lex_lineComment(BcLex *l) { @@ -68,7 +69,7 @@ void bc_lex_comment(BcLex *l) { if (BC_ERR(!c || buf[i + 1] == '\0')) { l->i = i; - bc_lex_err(l, BC_ERR_PARSE_COMMENT); + bc_lex_err(l, BC_ERROR_PARSE_COMMENT); } end = buf[i + 1] == '/'; @@ -142,7 +143,7 @@ void bc_lex_number(BcLex *l, char start) { if (c == 'e') { #if BC_ENABLED - if (BC_IS_POSIX) bc_lex_err(l, BC_ERR_POSIX_EXP_NUM); + if (BC_IS_POSIX) bc_lex_err(l, BC_ERROR_POSIX_EXP_NUM); #endif // BC_ENABLED bc_vec_push(&l->str, &c); @@ -156,7 +157,7 @@ void bc_lex_number(BcLex *l, char start) { } if (BC_ERR(!BC_LEX_NUM_CHAR(c, false, true))) - bc_lex_verr(l, BC_ERR_PARSE_CHAR, c); + bc_lex_verr(l, BC_ERROR_PARSE_CHAR, c); l->i += bc_lex_num(l, 0, true); } @@ -207,7 +208,7 @@ void bc_lex_next(BcLex *l) { l->last = l->t; l->line += (l->i != 0 && l->buf[l->i - 1] == '\n'); - if (BC_ERR(l->last == BC_LEX_EOF)) bc_lex_err(l, BC_ERR_PARSE_EOF); + if (BC_ERR(l->last == BC_LEX_EOF)) bc_lex_err(l, BC_ERROR_PARSE_EOF); l->t = BC_LEX_EOF; diff --git a/src/main.c b/src/main.c index 9c16e766e798..7e5e2905cf75 100644 --- a/src/main.c +++ b/src/main.c @@ -47,6 +47,9 @@ #include <bc.h> #include <dc.h> +char output_bufs[BC_VM_BUF_SIZE]; +BcVm vm; + int main(int argc, char *argv[]) { int s; diff --git a/src/num.c b/src/num.c index 0b8823a3fec2..de5fa5c566fb 100644 --- a/src/num.c +++ b/src/num.c @@ -41,6 +41,7 @@ #include <setjmp.h> #include <limits.h> +#include <status.h> #include <num.h> #include <rand.h> #include <vm.h> @@ -52,11 +53,11 @@ static inline ssize_t bc_num_neg(size_t n, bool neg) { } ssize_t bc_num_cmpZero(const BcNum *n) { - return bc_num_neg((n)->len != 0, BC_NUM_NEG(n)); + return bc_num_neg((n)->len != 0, (n)->neg); } static inline size_t bc_num_int(const BcNum *n) { - return n->len ? n->len - BC_NUM_RDX_VAL(n) : 0; + return n->len ? n->len - n->rdx : 0; } static void bc_num_expand(BcNum *restrict n, size_t req) { @@ -80,9 +81,10 @@ static void bc_num_setToZero(BcNum *restrict n, size_t scale) { assert(n != NULL); n->scale = scale; n->len = n->rdx = 0; + n->neg = false; } -void bc_num_zero(BcNum *restrict n) { +static inline void bc_num_zero(BcNum *restrict n) { bc_num_setToZero(n, 0); } @@ -96,11 +98,11 @@ 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; + if (BC_NUM_ZERO(n)) { + n->neg = false; + n->rdx = 0; } + else if (n->len < n->rdx) n->len = n->rdx; } static size_t bc_num_log10(size_t i) { @@ -124,7 +126,7 @@ static size_t bc_num_intDigits(const BcNum *n) { static size_t bc_num_nonzeroLen(const BcNum *restrict n) { size_t i, len = n->len; - assert(len == BC_NUM_RDX_VAL(n)); + assert(len == n->rdx); for (i = len - 1; i < len && !n->num[i]; --i); assert(i + 1 > 0); return i + 1; @@ -208,9 +210,9 @@ static void bc_num_mulArray(const BcNum *restrict a, BcBigDig b, 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); + assert(!c->neg || BC_NUM_NONZERO(c)); + assert(c->rdx <= c->len || !c->len); + assert(!c->len || c->num[c->len - 1] || c->rdx == c->len); } static void bc_num_divArray(const BcNum *restrict a, BcBigDig b, @@ -232,9 +234,9 @@ static void bc_num_divArray(const BcNum *restrict a, BcBigDig b, 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); + assert(!c->neg || BC_NUM_NONZERO(c)); + assert(c->rdx <= c->len || !c->len); + assert(!c->len || c->num[c->len - 1] || c->rdx == c->len); } static ssize_t bc_num_compare(const BcDig *restrict a, const BcDig *restrict b, @@ -248,7 +250,7 @@ static ssize_t bc_num_compare(const BcDig *restrict a, const BcDig *restrict b, ssize_t bc_num_cmp(const BcNum *a, const BcNum *b) { - size_t i, min, a_int, b_int, diff, ardx, brdx; + size_t i, min, a_int, b_int, diff; BcDig *max_num, *min_num; bool a_max, neg = false; ssize_t cmp; @@ -256,13 +258,13 @@ ssize_t bc_num_cmp(const BcNum *a, const BcNum *b) { 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(a)) return bc_num_neg(b->len != 0, !b->neg); if (BC_NUM_ZERO(b)) return bc_num_cmpZero(a); - if (BC_NUM_NEG(a)) { - if (BC_NUM_NEG(b)) neg = true; + if (a->neg) { + if (b->neg) neg = true; else return -1; } - else if (BC_NUM_NEG(b)) return 1; + else if (b->neg) return 1; a_int = bc_num_int(a); b_int = bc_num_int(b); @@ -270,19 +272,17 @@ ssize_t bc_num_cmp(const BcNum *a, const BcNum *b) { 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); + a_max = (a->rdx > b->rdx); if (a_max) { - min = brdx; - diff = ardx - brdx; + min = b->rdx; + diff = a->rdx - b->rdx; max_num = a->num + diff; min_num = b->num; } else { - min = ardx; - diff = brdx - ardx; + min = a->rdx; + diff = b->rdx - a->rdx; max_num = b->num + diff; min_num = a->num; } @@ -300,16 +300,15 @@ ssize_t bc_num_cmp(const BcNum *a, const BcNum *b) { void bc_num_truncate(BcNum *restrict n, size_t places) { - size_t nrdx, places_rdx; + size_t places_rdx; if (!places) return; - nrdx = BC_NUM_RDX_VAL(n); - places_rdx = nrdx ? nrdx - BC_NUM_RDX(n->scale - places) : 0; + places_rdx = n->rdx ? n->rdx - 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); + n->rdx -= places_rdx; if (BC_NUM_NONZERO(n)) { @@ -329,9 +328,9 @@ void bc_num_truncate(BcNum *restrict n, size_t places) { } } -void bc_num_extend(BcNum *restrict n, size_t places) { +static void bc_num_extend(BcNum *restrict n, size_t places) { - size_t nrdx, places_rdx; + size_t places_rdx; if (!places) return; if (BC_NUM_ZERO(n)) { @@ -339,8 +338,7 @@ void bc_num_extend(BcNum *restrict n, size_t places) { return; } - nrdx = BC_NUM_RDX_VAL(n); - places_rdx = BC_NUM_RDX(places + n->scale) - nrdx; + places_rdx = BC_NUM_RDX(places + n->scale) - n->rdx; if (places_rdx) { bc_num_expand(n, bc_vm_growSize(n->len, places_rdx)); @@ -348,11 +346,11 @@ void bc_num_extend(BcNum *restrict n, size_t places) { memset(n->num, 0, BC_NUM_SIZE(places_rdx)); } - BC_NUM_RDX_SET(n, nrdx + places_rdx); + n->rdx += places_rdx; n->scale += places; n->len += places_rdx; - assert(BC_NUM_RDX_VAL(n) == BC_NUM_RDX(n->scale)); + assert(n->rdx == BC_NUM_RDX(n->scale)); } static void bc_num_retireMul(BcNum *restrict n, size_t scale, @@ -362,7 +360,7 @@ static void bc_num_retireMul(BcNum *restrict n, size_t 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); + if (BC_NUM_NONZERO(n)) n->neg = (!neg1 != !neg2); } static void bc_num_split(const BcNum *restrict n, size_t idx, @@ -375,9 +373,7 @@ static void bc_num_split(const BcNum *restrict n, size_t idx, 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); + a->scale = a->rdx = b->scale = b->rdx = 0; assert(a->cap >= a->len); assert(b->cap >= b->len); @@ -396,7 +392,7 @@ static size_t bc_num_shiftZero(BcNum *restrict n) { size_t i; - assert(!BC_NUM_RDX_VAL(n) || BC_NUM_ZERO(n)); + assert(!n->rdx || BC_NUM_ZERO(n)); for (i = 0; i < n->len && !n->num[i]; ++i); @@ -442,7 +438,7 @@ static void bc_num_shiftLeft(BcNum *restrict n, size_t places) { 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 (size > SIZE_MAX - 1) bc_vm_err(BC_ERROR_MATH_OVERFLOW); } if (BC_NUM_ZERO(n)) { if (n->scale >= places) n->scale -= places; @@ -456,9 +452,7 @@ static void bc_num_shiftLeft(BcNum *restrict n, size_t places) { if (n->scale) { - size_t nrdx = BC_NUM_RDX_VAL(n); - - if (nrdx >= places_rdx) { + if (n->rdx >= places_rdx) { size_t mod = n->scale % BC_BASE_DIGS, revdig; @@ -468,7 +462,7 @@ static void bc_num_shiftLeft(BcNum *restrict n, size_t places) { if (mod + revdig > BC_BASE_DIGS) places_rdx = 1; else places_rdx = 0; } - else places_rdx -= nrdx; + else places_rdx -= n->rdx; } if (places_rdx) { @@ -478,13 +472,10 @@ static void bc_num_shiftLeft(BcNum *restrict n, size_t places) { n->len += places_rdx; } - if (places > n->scale) { - n->scale = 0; - BC_NUM_RDX_SET(n, 0); - } + if (places > n->scale) n->scale = n->rdx = 0; else { n->scale -= places; - BC_NUM_RDX_SET(n, BC_NUM_RDX(n->scale)); + n->rdx = BC_NUM_RDX(n->scale); } if (shift) bc_num_shift(n, BC_BASE_DIGS - dig); @@ -492,7 +483,7 @@ static void bc_num_shiftLeft(BcNum *restrict n, size_t places) { bc_num_clean(n); } -void bc_num_shiftRight(BcNum *restrict n, size_t places) { +static void bc_num_shiftRight(BcNum *restrict n, size_t places) { BcBigDig dig; size_t places_rdx, scale, scale_mod, int_len, expand; @@ -529,18 +520,17 @@ void bc_num_shiftRight(BcNum *restrict n, size_t places) { 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); + n->scale = n->rdx = 0; if (shift) bc_num_shift(n, dig); n->scale = scale + places; - BC_NUM_RDX_SET(n, BC_NUM_RDX(n->scale)); + n->rdx = 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)); + assert(n->rdx <= n->len && n->len <= n->cap); + assert(n->rdx == BC_NUM_RDX(n->scale)); } static void bc_num_inv(BcNum *a, BcNum *b, size_t scale) { @@ -560,7 +550,7 @@ static void bc_num_inv(BcNum *a, BcNum *b, size_t scale) { 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); + if (BC_ERR(b->rdx)) bc_vm_err(BC_ERROR_MATH_NON_INTEGER); bc_num_copy(c, a); bc_num_bigdig(b, v); } @@ -570,8 +560,8 @@ 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; + size_t len_l, len_r; + bool b_neg, do_sub, do_rev_sub, carry; // 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. @@ -583,25 +573,23 @@ static void bc_num_as(BcNum *a, BcNum *b, BcNum *restrict c, size_t sub) { } if (BC_NUM_ZERO(a)) { bc_num_copy(c, b); - c->rdx = BC_NUM_NEG_VAL(c, BC_NUM_NEG(b) != sub); + c->neg = (b->neg != 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); + b_neg = (b->neg != sub); // Actually add the numbers if their signs are equal, else subtract. - do_sub = (BC_NUM_NEG(a) != b_neg); + do_sub = (a->neg != 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); + min_rdx = BC_MIN(a->rdx, b->rdx); + max_rdx = BC_MAX(a->rdx, b->rdx); diff = max_rdx - min_rdx; max_len = max_int + max_rdx; @@ -610,7 +598,7 @@ static void bc_num_as(BcNum *a, BcNum *b, BcNum *restrict c, size_t 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) + else if (a->rdx > b->rdx) 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); @@ -646,9 +634,9 @@ static void bc_num_as(BcNum *a, BcNum *b, BcNum *restrict c, size_t sub) { // 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) { + if ((a->rdx > b->rdx) != do_rev_sub) { - // !do_rev_sub && ardx > brdx || do_rev_sub && brdx > ardx + // !do_rev_sub && a->rdx > b->rdx || do_rev_sub && b->rdx > a->rdx // 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)); @@ -661,14 +649,14 @@ static void bc_num_as(BcNum *a, BcNum *b, BcNum *restrict c, size_t sub) { // or subtracted from zero (in case of a subtraction). if (do_sub) { - // do_sub (do_rev_sub && ardx > brdx || - // !do_rev_sub && brdx > ardx) + // do_sub (do_rev_sub && a->rdx > b->rdx || + // !do_rev_sub && b->rdx > a->rdx) for (i = 0; i < diff; i++) ptr_c[i] = bc_num_subDigits(0, ptr_r[i], &carry); } else { - // !do_sub && brdx > ardx + // !do_sub && b->rdx > a->rdx memcpy(ptr_c, ptr_r, BC_NUM_SIZE(diff)); } @@ -703,9 +691,9 @@ static void bc_num_as(BcNum *a, BcNum *b, BcNum *restrict c, size_t sub) { // 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->neg = (a->neg != (do_sub && do_rev_sub)); c->len = max_len; + c->rdx = max_rdx; c->scale = BC_MAX(a->scale, b->scale); bc_num_clean(c); @@ -718,7 +706,7 @@ static void bc_num_m_simp(const BcNum *a, const BcNum *b, BcNum *restrict c) BcBigDig sum = 0, carry = 0; assert(sizeof(sum) >= sizeof(BcDig) * 2); - assert(!BC_NUM_RDX_VAL(a) && !BC_NUM_RDX_VAL(b)); + assert(!a->rdx && !b->rdx); clen = bc_vm_growSize(alen, blen); bc_num_expand(c, bc_vm_growSize(clen, 1)); @@ -763,7 +751,7 @@ 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)); + assert(!n->rdx && !a->rdx); op(n->num + shift, a->num, a->len); } @@ -780,7 +768,7 @@ static void bc_num_k(BcNum *a, BcNum *b, BcNum *restrict 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); + if ((aone && a->neg) || b->neg) c->neg = !c->neg; return; } if (a->len < BC_NUM_KARATSUBA_LEN || b->len < BC_NUM_KARATSUBA_LEN) { @@ -832,9 +820,6 @@ static void bc_num_k(BcNum *a, BcNum *b, BcNum *restrict c) { 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); @@ -844,9 +829,6 @@ static void bc_num_k(BcNum *a, BcNum *b, BcNum *restrict c) { 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); @@ -856,14 +838,10 @@ static void bc_num_k(BcNum *a, BcNum *b, BcNum *restrict c) { 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; + op = (m1.neg != m2.neg) ? bc_num_subArrays : bc_num_addArrays; bc_num_shiftAddSub(c, &z1, max2, op); } @@ -882,9 +860,6 @@ 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; @@ -910,19 +885,15 @@ static void bc_num_m(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { 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)); + if (BC_NUM_NONZERO(c)) c->neg = (a->neg != b->neg); 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_num_init(&cpa, a->len + a->rdx); + bc_num_init(&cpb, b->len + b->rdx); BC_SETJMP_LOCKED(err); @@ -931,19 +902,12 @@ static void bc_num_m(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { 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); + cpa.neg = cpb.neg = false; - assert(BC_NUM_RDX_VALID_NP(cpa)); - assert(BC_NUM_RDX_VALID_NP(cpb)); - - ardx = BC_NUM_RDX_VAL_NP(cpa) * BC_BASE_DIGS; + ardx = cpa.rdx * BC_BASE_DIGS; bc_num_shiftLeft(&cpa, ardx); - brdx = BC_NUM_RDX_VAL_NP(cpb) * BC_BASE_DIGS; + brdx = cpb.rdx * BC_BASE_DIGS; bc_num_shiftLeft(&cpb, brdx); // We need to reset the jump here because azero and bzero are used in the @@ -972,7 +936,7 @@ static void bc_num_m(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { 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)); + bc_num_retireMul(c, scale, a->neg, b->neg); err: BC_SIG_MAYLOCK; @@ -1033,7 +997,7 @@ static void bc_num_d_long(BcNum *restrict a, BcNum *restrict b, 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->rdx = a->rdx; c->scale = a->scale; c->len = a->len; @@ -1066,7 +1030,7 @@ static void bc_num_d_long(BcNum *restrict a, BcNum *restrict b, memset(c->num, 0, BC_NUM_SIZE(c->cap)); assert(c->scale >= scale); - rdx = BC_NUM_RDX_VAL(c) - BC_NUM_RDX(scale); + rdx = c->rdx - BC_NUM_RDX(scale); BC_SIG_LOCK; @@ -1130,27 +1094,27 @@ err: static void bc_num_d(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { - size_t len, cpardx; + size_t len; BcNum cpa, cpb; - if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO); + if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERROR_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)); + bc_num_retireMul(c, scale, a->neg, b->neg); return; } - if (!BC_NUM_RDX_VAL(a) && !BC_NUM_RDX_VAL(b) && b->len == 1 && !scale) { + if (!a->rdx && !b->rdx && 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)); + bc_num_retireMul(c, scale, a->neg, b->neg); return; } - len = bc_num_divReq(a, b, scale); + len = bc_num_mulReq(a, b, scale); BC_SIG_LOCK; @@ -1169,18 +1133,15 @@ static void bc_num_d(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { bc_num_extend(&cpa, (len - cpa.len) * BC_BASE_DIGS); } - cpardx = BC_NUM_RDX_VAL_NP(cpa); - cpa.scale = cpardx * BC_BASE_DIGS; + cpa.scale = cpa.rdx * 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; + cpa.rdx -= BC_NUM_RDX(b->scale); + cpa.scale = cpa.rdx * 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; + cpa.scale = cpa.rdx * BC_BASE_DIGS; } if (cpa.cap == cpa.len) bc_num_expand(&cpa, bc_vm_growSize(cpa.len, 1)); @@ -1188,14 +1149,13 @@ static void bc_num_d(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { // 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); + if (cpa.rdx == cpa.len) cpa.len = bc_num_nonzeroLen(&cpa); + if (cpb.rdx == cpb.len) cpb.len = bc_num_nonzeroLen(&cpb); + cpb.scale = cpb.rdx = 0; bc_num_d_long(&cpa, &cpb, c, scale); - bc_num_retireMul(c, scale, BC_NUM_NEG(a), BC_NUM_NEG(b)); + bc_num_retireMul(c, scale, a->neg, b->neg); err: BC_SIG_MAYLOCK; @@ -1210,7 +1170,7 @@ static void bc_num_r(BcNum *a, BcNum *b, BcNum *restrict c, BcNum temp; bool neg; - if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO); + if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERROR_MATH_DIVIDE_BY_ZERO); if (BC_NUM_ZERO(a)) { bc_num_setToZero(c, ts); bc_num_setToZero(d, ts); @@ -1229,17 +1189,14 @@ static void bc_num_r(BcNum *a, BcNum *b, BcNum *restrict c, 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); + neg = d->neg; + bc_num_retireMul(d, ts, a->neg, b->neg); + d->neg = BC_NUM_NONZERO(d) ? neg : false; err: BC_SIG_MAYLOCK; @@ -1278,29 +1235,29 @@ static void bc_num_p(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { 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_ERR(b->rdx)) bc_vm_err(BC_ERROR_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); + if (b->neg) bc_vm_err(BC_ERROR_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); + if (!b->neg) 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); + neg = b->neg; + b->neg = false; bc_num_bigdig(b, &pow); - b->rdx = BC_NUM_NEG_VAL(b, neg); + b->neg = neg; bc_num_createCopy(©, a); @@ -1315,7 +1272,6 @@ static void bc_num_p(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { for (powrdx = a->scale; !(pow & 1); pow >>= 1) { powrdx <<= 1; - assert(BC_NUM_RDX_VALID_NP(copy)); bc_num_mul(©, ©, ©, powrdx); } @@ -1325,13 +1281,10 @@ static void bc_num_p(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { while (pow >>= 1) { powrdx <<= 1; - assert(BC_NUM_RDX_VALID_NP(copy)); bc_num_mul(©, ©, ©, powrdx); if (pow & 1) { resrdx += powrdx; - assert(BC_NUM_RDX_VALID(c)); - assert(BC_NUM_RDX_VALID_NP(copy)); bc_num_mul(c, ©, c, resrdx); } } @@ -1391,14 +1344,11 @@ static void bc_num_right(BcNum *a, BcNum *b, BcNum *restrict c, size_t scale) { static void bc_num_binary(BcNum *a, BcNum *b, BcNum *c, size_t scale, BcNumBinaryOp op, size_t req) { - BcNum *ptr_a, *ptr_b, num2; + BcNum num2, *ptr_a, *ptr_b; 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) { @@ -1408,9 +1358,7 @@ static void bc_num_binary(BcNum *a, BcNum *b, BcNum *c, size_t scale, memcpy(ptr_a, c, sizeof(BcNum)); init = true; } - else { - ptr_a = a; - } + else ptr_a = a; if (c == b) { @@ -1421,9 +1369,7 @@ static void bc_num_binary(BcNum *a, BcNum *b, BcNum *c, size_t scale, init = true; } } - else { - ptr_b = b; - } + else ptr_b = b; if (init) { @@ -1439,10 +1385,9 @@ static void bc_num_binary(BcNum *a, BcNum *b, BcNum *c, size_t scale, 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); + assert(!c->neg || BC_NUM_NONZERO(c)); + assert(c->rdx <= c->len || !c->len); + assert(!c->len || c->num[c->len - 1] || c->rdx == c->len); err: if (init) { @@ -1452,8 +1397,8 @@ err: } } -#if !defined(NDEBUG) || BC_ENABLE_LIBRARY -bool bc_num_strValid(const char *restrict val) { +#ifndef NDEBUG +static bool bc_num_strValid(const char *val) { bool radix = false; size_t i, len = strlen(val); @@ -1477,7 +1422,7 @@ bool bc_num_strValid(const char *restrict val) { return true; } -#endif // !defined(NDEBUG) || BC_ENABLE_LIBRARY +#endif // NDEBUG static BcBigDig bc_num_parseChar(char c, size_t base_t) { @@ -1514,8 +1459,8 @@ static void bc_num_parseDecimal(BcNum *restrict n, const char *restrict val) { n->scale = (size_t) (rdx * (((uintptr_t) (val + len)) - (((uintptr_t) ptr) + 1))); + n->rdx = BC_NUM_RDX(n->scale); - 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; @@ -1525,11 +1470,7 @@ static void bc_num_parseDecimal(BcNum *restrict n, const char *restrict val) { 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; - } + if (zero) n->len = n->rdx = 0; else { BcBigDig exp, pow; @@ -1610,8 +1551,6 @@ static void bc_num_parseBase(BcNum *restrict n, const char *restrict val, 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); @@ -1620,9 +1559,7 @@ static void bc_num_parseBase(BcNum *restrict n, const char *restrict val, 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; + if (m2->len < m2->rdx) m2->len = m2->rdx; ptr = m1; m1 = m2; @@ -1652,13 +1589,11 @@ int_err: BC_LONGJMP_CONT; } -static inline void bc_num_printNewline(void) { -#if !BC_ENABLE_LIBRARY +static void bc_num_printNewline(void) { if (vm.nchars >= vm.line_len - 1) { bc_vm_putchar('\\'); bc_vm_putchar('\n'); } -#endif // !BC_ENABLE_LIBRARY } static void bc_num_putchar(int c) { @@ -1666,14 +1601,14 @@ static void bc_num_putchar(int c) { bc_vm_putchar(c); } -#if DC_ENABLED && !BC_ENABLE_LIBRARY +#if DC_ENABLED 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); } -#endif // DC_ENABLED && !BC_ENABLE_LIBRARY +#endif // DC_ENABLED static void bc_num_printDigits(size_t n, size_t len, bool rdx) { @@ -1703,11 +1638,11 @@ static void bc_num_printHex(size_t n, size_t len, bool rdx) { static void bc_num_printDecimal(const BcNum *restrict n) { - size_t i, j, rdx = BC_NUM_RDX_VAL(n); + size_t i, j, rdx = n->rdx; bool zero = true; size_t buffer[BC_BASE_DIGS]; - if (BC_NUM_NEG(n)) bc_num_putchar('-'); + if (n->neg) bc_num_putchar('-'); for (i = n->len - 1; i < n->len; --i) { @@ -1737,9 +1672,9 @@ static void bc_num_printDecimal(const BcNum *restrict n) { #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); + bool neg = (n->len <= n->rdx); BcNum temp, exp; + size_t places, mod; BcDig digs[BC_NUM_BIGDIG_LOG10]; BC_SIG_LOCK; @@ -1761,7 +1696,7 @@ static void bc_num_printExponent(const BcNum *restrict n, bool eng) { else break; } - places += (nrdx - (idx + 1)) * BC_BASE_DIGS; + places += (n->rdx - (idx + 1)) * BC_BASE_DIGS; mod = places % 3; if (eng && mod != 0) places += 3 - mod; @@ -1864,7 +1799,7 @@ static void bc_num_printNum(BcNum *restrict n, BcBigDig base, BcVec stack; BcNum intp, fracp1, fracp2, digit, flen1, flen2, *n1, *n2, *temp; BcBigDig dig = 0, *ptr, acc, exp; - size_t i, j, nrdx; + size_t i, j; bool radix; BcDig digit_digs[BC_NUM_BIGDIG_LOG10 + 1]; @@ -1908,12 +1843,10 @@ static void bc_num_printNum(BcNum *restrict n, BcBigDig base, // 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_init(&fracp1, n->rdx); bc_num_createCopy(&intp, n); @@ -1978,7 +1911,7 @@ static void bc_num_printNum(BcNum *restrict n, BcBigDig base, BC_UNSETJMP; - bc_num_init(&fracp2, nrdx); + bc_num_init(&fracp2, n->rdx); 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); @@ -1994,16 +1927,13 @@ static void bc_num_printNum(BcNum *restrict n, BcBigDig base, n2 = &flen2; fracp2.scale = n->scale; - BC_NUM_RDX_SET_NP(fracp2, BC_NUM_RDX(fracp2.scale)); + fracp2.rdx = 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; + if (fracp2.len < fracp2.rdx) fracp2.len = fracp2.rdx; // fracp is guaranteed to be non-negative and small enough. bc_num_bigdig2(&fracp2, &dig); @@ -2037,11 +1967,11 @@ static void bc_num_printBase(BcNum *restrict n, BcBigDig base) { size_t width; BcNumDigitOp print; - bool neg = BC_NUM_NEG(n); + bool neg = n->neg; if (neg) bc_num_putchar('-'); - BC_NUM_NEG_CLR(n); + n->neg = false; if (base <= BC_NUM_MAX_POSIX_IBASE) { width = 1; @@ -2054,14 +1984,14 @@ static void bc_num_printBase(BcNum *restrict n, BcBigDig base) { } bc_num_printNum(n, base, width, print); - n->rdx = BC_NUM_NEG_VAL(n, neg); + n->neg = neg; } -#if DC_ENABLED && !BC_ENABLE_LIBRARY +#if DC_ENABLED void bc_num_stream(BcNum *restrict n, BcBigDig base) { bc_num_printNum(n, base, 1, bc_num_printChar); } -#endif // DC_ENABLED && !BC_ENABLE_LIBRARY +#endif // DC_ENABLED void bc_num_setup(BcNum *restrict n, BcDig *restrict num, size_t cap) { assert(n != NULL); @@ -2112,7 +2042,7 @@ void bc_num_copy(BcNum *d, const BcNum *s) { if (d == s) return; bc_num_expand(d, s->len); d->len = s->len; - // I can just copy directly here. + d->neg = s->neg; d->rdx = s->rdx; d->scale = s->scale; memcpy(d->num, s->num, BC_NUM_SIZE(d->len)); @@ -2126,7 +2056,7 @@ void bc_num_createCopy(BcNum *d, const BcNum *s) { void bc_num_createFromBigdig(BcNum *n, BcBigDig val) { BC_SIG_ASSERT_LOCKED; - bc_num_init(n, BC_NUM_BIGDIG_LOG10); + bc_num_init(n, (BC_NUM_BIGDIG_LOG10 - 1) / BC_BASE_DIGS + 1); bc_num_bigdig2num(n, val); } @@ -2140,7 +2070,7 @@ size_t bc_num_len(const BcNum *restrict n) { if (BC_NUM_ZERO(n)) return 0; - if (BC_NUM_RDX_VAL(n) == len) { + if (n->rdx == len) { size_t zero, scale; @@ -2158,20 +2088,19 @@ size_t bc_num_len(const BcNum *restrict n) { return len; } -void bc_num_parse(BcNum *restrict n, const char *restrict val, BcBigDig base) { - +void bc_num_parse(BcNum *restrict n, const char *restrict val, + BcBigDig base, bool letter) +{ 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]) { + if (letter) { 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) { @@ -2184,7 +2113,8 @@ void bc_num_print(BcNum *restrict n, BcBigDig base, bool newline) { 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); + else if (base == 0 || base == 1) + bc_num_printExponent(n, base != 0); #endif // BC_ENABLE_EXTRA_MATH else bc_num_printBase(n, base); @@ -2197,38 +2127,28 @@ void bc_num_bigdig2(const BcNum *restrict n, BcBigDig *result) { // 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. + // negative errors or overflow. We also don't care about signals because + // this function should execute in only a few iterations, meaning that + // ignoring signals here should be fine. BcBigDig r = 0; - size_t nrdx = BC_NUM_RDX_VAL(n); assert(n != NULL && result != NULL); - assert(!BC_NUM_NEG(n)); + assert(!n->neg); assert(bc_num_cmp(n, &vm.max) < 0); - assert(n->len - nrdx <= 3); + assert(n->len - n->rdx <= 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) { - + switch (n->len - n->rdx) { case 3: - { - r = (BcBigDig) n->num[nrdx + 2]; - } - // Fallthrough. - BC_FALLTHROUGH - + r = (BcBigDig) n->num[n->rdx + 2]; + // Fallthrough. case 2: - { - r = r * BC_BASE_POW + (BcBigDig) n->num[nrdx + 1]; - } - // Fallthrough. - BC_FALLTHROUGH - + r = r * BC_BASE_POW + (BcBigDig) n->num[n->rdx + 1]; + // Fallthrough. case 1: - { - r = r * BC_BASE_POW + (BcBigDig) n->num[nrdx]; - } + r = r * BC_BASE_POW + (BcBigDig) n->num[n->rdx]; } *result = r; @@ -2238,9 +2158,9 @@ 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(n->neg)) bc_vm_err(BC_ERROR_MATH_NEGATIVE); if (BC_ERR(bc_num_cmp(n, &vm.max) >= 0)) - bc_vm_err(BC_ERR_MATH_OVERFLOW); + bc_vm_err(BC_ERROR_MATH_OVERFLOW); bc_num_bigdig2(n, result); } @@ -2267,41 +2187,41 @@ void bc_num_bigdig2num(BcNum *restrict n, BcBigDig val) { #if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND void bc_num_rng(const BcNum *restrict n, BcRNG *rng) { - BcNum temp, temp2, intn, frac; + BcNum pow, temp, temp2, intn, frac; BcRand state1, state2, inc1, inc2; - size_t nrdx = BC_NUM_RDX_VAL(n); + BcDig pow_num[BC_RAND_NUM_SIZE]; + + bc_num_setup(&pow, pow_num, sizeof(pow_num) / sizeof(BcDig)); BC_SIG_LOCK; bc_num_init(&temp, n->len); bc_num_init(&temp2, n->len); - bc_num_init(&frac, nrdx); + bc_num_init(&frac, n->rdx); bc_num_init(&intn, bc_num_int(n)); BC_SETJMP_LOCKED(err); BC_SIG_UNLOCK; - assert(BC_NUM_RDX_VALID_NP(vm.max)); + bc_num_mul(&vm.max, &vm.max, &pow, 0); - memcpy(frac.num, n->num, BC_NUM_SIZE(nrdx)); - frac.len = nrdx; - BC_NUM_RDX_SET_NP(frac, nrdx); + memcpy(frac.num, n->num, BC_NUM_SIZE(n->rdx)); + frac.len = n->rdx; + frac.rdx = n->rdx; 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_mul(&frac, &pow, &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))); + memcpy(intn.num, n->num + n->rdx, 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. + // the use of BC_ERROR_SIGNAL_ONLY() on each of the divmod's and mod's + // below. assert(BC_NUM_NONZERO(&vm.max)); if (BC_NUM_NONZERO(&frac)) { @@ -2351,7 +2271,8 @@ err: void bc_num_createFromRNG(BcNum *restrict n, BcRNG *rng) { BcRand s1, s2, i1, i2; - BcNum conv, temp1, temp2, temp3; + BcNum pow, conv, temp1, temp2, temp3; + BcDig pow_num[BC_RAND_NUM_SIZE]; BcDig temp1_num[BC_RAND_NUM_SIZE], temp2_num[BC_RAND_NUM_SIZE]; BcDig conv_num[BC_NUM_BIGDIG_LOG10]; @@ -2363,36 +2284,35 @@ void bc_num_createFromRNG(BcNum *restrict n, BcRNG *rng) { BC_SIG_UNLOCK; + bc_num_setup(&pow, pow_num, sizeof(pow_num) / sizeof(BcDig)); 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. + // the assumption that pow 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_num_mul(&vm.max, &vm.max, &pow, 0); + + // Because this is true, we can just use BC_ERROR_SIGNAL_ONLY() below when + // dividing by pow. + assert(BC_NUM_NONZERO(&pow)); 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_div(&temp2, &pow, &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); @@ -2401,8 +2321,6 @@ void bc_num_createFromRNG(BcNum *restrict n, BcRNG *rng) { bc_num_add(&temp2, &temp3, n, 0); - assert(BC_NUM_RDX_VALID(n)); - err: BC_SIG_MAYLOCK; bc_num_free(&temp3); @@ -2422,8 +2340,8 @@ void bc_num_irand(const BcNum *restrict a, BcNum *restrict b, 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_ERR(a->neg)) bc_vm_err(BC_ERROR_MATH_NEGATIVE); + if (BC_ERR(a->rdx)) bc_vm_err(BC_ERROR_MATH_NON_INTEGER); if (BC_NUM_ZERO(a) || BC_NUM_ONE(a)) return; cmp = bc_num_cmp(a, &vm.max); @@ -2478,7 +2396,8 @@ void bc_num_irand(const BcNum *restrict a, BcNum *restrict b, 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. + // the use of BC_ERROR_SIGNAL_ONLY() on each of the divmod's and mod's + // below. assert(BC_NUM_NONZERO(&vm.max)); while (BC_NUM_NONZERO(c1)) { @@ -2510,17 +2429,11 @@ void bc_num_irand(const BcNum *restrict a, BcNum *restrict b, 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; @@ -2541,8 +2454,6 @@ void bc_num_irand(const BcNum *restrict a, BcNum *restrict b, bc_num_copy(b, t1); bc_num_clean(b); - assert(BC_NUM_RDX_VALID(b)); - err: BC_SIG_MAYLOCK; bc_num_free(&pow); @@ -2562,11 +2473,11 @@ size_t bc_num_addReq(const BcNum *a, const BcNum *b, size_t scale) { BC_UNUSED(scale); - ardx = BC_NUM_RDX_VAL(a); + ardx = a->rdx; aint = bc_num_int(a); assert(aint <= a->len && ardx <= a->len); - brdx = BC_NUM_RDX_VAL(b); + brdx = b->rdx; bint = bc_num_int(b); assert(bint <= b->len && brdx <= b->len); @@ -2578,22 +2489,13 @@ 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 max, rdx; - rdx = bc_vm_growSize(BC_NUM_RDX_VAL(a), BC_NUM_RDX_VAL(b)); + rdx = bc_vm_growSize(a->rdx, b->rdx); 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); @@ -2602,62 +2504,44 @@ 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) { BC_UNUSED(scale); - return a->len + b->len - BC_NUM_RDX_VAL(a) - BC_NUM_RDX_VAL(b); + return a->len + b->len - a->rdx - b->rdx; } #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)); + bc_num_binary(a, b, c, scale, bc_num_d, bc_num_mulReq(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)); + bc_num_binary(a, b, c, scale, bc_num_rem, bc_num_mulReq(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 @@ -2670,13 +2554,13 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { assert(a != NULL && b != NULL && a != b); - if (BC_ERR(BC_NUM_NEG(a))) bc_vm_err(BC_ERR_MATH_NEGATIVE); + if (BC_ERR(a->neg)) bc_vm_err(BC_ERROR_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); + req = bc_vm_growSize(BC_MAX(rdx, a->rdx), len >> 1); BC_SIG_LOCK; @@ -2684,9 +2568,6 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { 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; @@ -2698,7 +2579,7 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { } rdx = BC_NUM_RDX(scale); - rdx = BC_MAX(rdx, BC_NUM_RDX_VAL(a)); + rdx = BC_MAX(rdx, a->rdx); len = bc_vm_growSize(a->len, rdx); BC_SIG_LOCK; @@ -2710,7 +2591,7 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { bc_num_one(&half); half.num[0] = BC_BASE_POW / 2; half.len = 1; - BC_NUM_RDX_SET_NP(half, 1); + half.rdx = 1; half.scale = 1; bc_num_init(&f, len); @@ -2735,7 +2616,6 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { bc_num_shiftLeft(x0, pow / 2); } - // I can set the rdx here directly because neg should be false. x0->scale = x0->rdx = digs = digs1 = digs2 = 0; resscale = (scale + BC_BASE_DIGS) + 2; @@ -2745,10 +2625,6 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { 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; @@ -2759,10 +2635,9 @@ void bc_num_sqrt(BcNum *restrict a, BcNum *restrict b, size_t scale) { 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); + assert(!b->neg || BC_NUM_NONZERO(b)); + assert(b->rdx <= b->len || !b->len); + assert(!b->len || b->num[b->len - 1] || b->rdx == b->len); err: BC_SIG_MAYLOCK; @@ -2775,9 +2650,9 @@ err: void bc_num_divmod(BcNum *a, BcNum *b, BcNum *c, BcNum *d, size_t scale) { - size_t ts, len; - BcNum *ptr_a, num2; + BcNum num2, *ptr_a; bool init = false; + size_t ts, len; ts = BC_MAX(scale + b->scale, a->scale); len = bc_num_mulReq(a, b, ts); @@ -2805,9 +2680,8 @@ void bc_num_divmod(BcNum *a, BcNum *b, BcNum *c, BcNum *d, size_t scale) { bc_num_expand(c, len); } - if (BC_NUM_NONZERO(a) && !BC_NUM_RDX_VAL(a) && - !BC_NUM_RDX_VAL(b) && b->len == 1 && !scale) - { + if (BC_NUM_NONZERO(a) && !a->rdx && !b->rdx && b->len == 1 && !scale) { + BcBigDig rem; bc_num_divArray(ptr_a, (BcBigDig) b->num[0], c, &rem); @@ -2819,14 +2693,12 @@ void bc_num_divmod(BcNum *a, BcNum *b, BcNum *c, BcNum *d, size_t scale) { } 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); + assert(!c->neg || BC_NUM_NONZERO(c)); + assert(c->rdx <= c->len || !c->len); + assert(!c->len || c->num[c->len - 1] || c->rdx == c->len); + assert(!d->neg || BC_NUM_NONZERO(d)); + assert(d->rdx <= d->len || !d->len); + assert(!d->len || d->num[d->len - 1] || d->rdx == d->len); err: if (init) { @@ -2845,10 +2717,10 @@ void bc_num_modexp(BcNum *a, BcNum *b, BcNum *c, BcNum *restrict d) { 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); + if (BC_ERR(BC_NUM_ZERO(c))) bc_vm_err(BC_ERROR_MATH_DIVIDE_BY_ZERO); + if (BC_ERR(b->neg)) bc_vm_err(BC_ERROR_MATH_NEGATIVE); + if (BC_ERR(a->rdx || b->rdx || c->rdx)) + bc_vm_err(BC_ERROR_MATH_NON_INTEGER); bc_num_expand(d, c->len); @@ -2875,10 +2747,7 @@ void bc_num_modexp(BcNum *a, BcNum *b, BcNum *c, BcNum *restrict d) { // 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)); + if (BC_NUM_ONE(&temp) && !temp.neg) { bc_num_mul(d, &base, &temp, 0); @@ -2886,8 +2755,6 @@ void bc_num_modexp(BcNum *a, BcNum *b, BcNum *c, BcNum *restrict d) { 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. @@ -2900,9 +2767,8 @@ err: 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); + assert(!d->neg || d->len); + assert(!d->len || d->num[d->len - 1] || d->rdx == d->len); } #endif // DC_ENABLED @@ -2931,7 +2797,7 @@ void bc_num_printDigs(const BcDig *n, size_t len, bool emptyline) { void bc_num_printWithDigs(const BcNum *n, const char *name, bool emptyline) { bc_file_puts(&vm.fout, name); bc_file_printf(&vm.fout, " len: %zu, rdx: %zu, scale: %zu\n", - name, n->len, BC_NUM_RDX_VAL(n), n->scale); + name, n->len, n->rdx, n->scale); bc_num_printDigs(n->num, n->len, emptyline); } @@ -2940,13 +2806,13 @@ 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 "); + n->len ? (n->neg ? "-" : "+") : "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 == n->rdx) bc_file_puts(&vm.ferr, ". "); - if (scale / BC_BASE_DIGS != BC_NUM_RDX_VAL(n) - i - 1) + if (scale / BC_BASE_DIGS != n->rdx - i - 1) bc_file_printf(&vm.ferr, "%lu ", (unsigned long) n->num[i]); else { @@ -2965,7 +2831,7 @@ void bc_num_dump(const char *varname, const BcNum *n) { } bc_file_printf(&vm.ferr, "(%zu | %zu.%zu / %zu) %lu\n", - n->scale, n->len, BC_NUM_RDX_VAL(n), n->cap, + n->scale, n->len, n->rdx, n->cap, (unsigned long) (void*) n->num); } #endif // BC_DEBUG_CODE diff --git a/src/opt.c b/src/opt.c index 57cee759af5e..3a01a2657f15 100644 --- a/src/opt.c +++ b/src/opt.c @@ -62,8 +62,8 @@ static const char* bc_opt_longopt(const BcOptLong *longopts, int c) { return "NULL"; } -static void bc_opt_error(BcErr err, int c, const char *str) { - if (err == BC_ERR_FATAL_OPTION) bc_vm_error(err, 0, str); +static void bc_opt_error(BcError err, int c, const char *str) { + if (err == BC_ERROR_FATAL_OPTION) bc_vm_error(err, 0, str); else bc_vm_error(err, 0, (int) c, str); } @@ -110,12 +110,10 @@ static int bc_opt_parseShort(BcOpt *o, const BcOptLong *longopts) { str[0] = option[0]; o->optind += 1; - bc_opt_error(BC_ERR_FATAL_OPTION, option[0], str); + bc_opt_error(BC_ERROR_FATAL_OPTION, option[0], str); } } // Fallthrough. - BC_FALLTHROUGH - case BC_OPT_NONE: { if (option[1]) o->subopt += 1; @@ -138,7 +136,7 @@ static int bc_opt_parseShort(BcOpt *o, const BcOptLong *longopts) { o->optarg = next; o->optind += 1; } - else bc_opt_error(BC_ERR_FATAL_OPTION_NO_ARG, option[0], + else bc_opt_error(BC_ERROR_FATAL_OPTION_NO_ARG, option[0], bc_opt_longopt(longopts, option[0])); @@ -217,12 +215,12 @@ int bc_opt_parse(BcOpt *o, const BcOptLong *longopts) { if ((longopts[i].type == BC_OPT_BC_ONLY && BC_IS_DC) || (longopts[i].type == BC_OPT_DC_ONLY && BC_IS_BC)) { - bc_opt_error(BC_ERR_FATAL_OPTION, o->optopt, name); + bc_opt_error(BC_ERROR_FATAL_OPTION, o->optopt, name); } if (longopts[i].type == BC_OPT_NONE && arg != NULL) { - bc_opt_error(BC_ERR_FATAL_OPTION_ARG, o->optopt, name); + bc_opt_error(BC_ERROR_FATAL_OPTION_ARG, o->optopt, name); } if (arg != NULL) o->optarg = arg; @@ -231,7 +229,7 @@ int bc_opt_parse(BcOpt *o, const BcOptLong *longopts) { o->optarg = o->argv[o->optind]; if (o->optarg != NULL) o->optind += 1; - else bc_opt_error(BC_ERR_FATAL_OPTION_NO_ARG, + else bc_opt_error(BC_ERROR_FATAL_OPTION_NO_ARG, o->optopt, name); } @@ -239,7 +237,7 @@ int bc_opt_parse(BcOpt *o, const BcOptLong *longopts) { } } - bc_opt_error(BC_ERR_FATAL_OPTION, 0, option); + bc_opt_error(BC_ERROR_FATAL_OPTION, 0, option); return -1; } diff --git a/src/parse.c b/src/parse.c index 39b79efdd02f..a48f5807e9ce 100644 --- a/src/parse.c +++ b/src/parse.c @@ -40,6 +40,9 @@ #include <limits.h> +#include <status.h> +#include <vector.h> +#include <lex.h> #include <parse.h> #include <program.h> #include <vm.h> diff --git a/src/program.c b/src/program.c index f0a67ee194c1..3c2544f8a61f 100644 --- a/src/program.c +++ b/src/program.c @@ -61,7 +61,7 @@ static inline void bc_program_type_num(BcResult *r, BcNum *n) { 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_ERR(!BC_PROG_NUM(r, n))) bc_vm_err(BC_ERROR_EXEC_TYPE); } #if BC_ENABLED @@ -72,7 +72,7 @@ static void bc_program_type_match(BcResult *r, BcType t) { #endif // DC_ENABLED if (BC_ERR((r->t != BC_RESULT_ARRAY) != (!t))) - bc_vm_err(BC_ERR_EXEC_TYPE); + bc_vm_err(BC_ERROR_EXEC_TYPE); } #endif // BC_ENABLED @@ -270,7 +270,7 @@ static void bc_program_operand(BcProgram *p, BcResult **r, *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); + if (BC_ERR((*r)->t == BC_RESULT_VOID)) bc_vm_err(BC_ERROR_EXEC_VOID_VAL); #endif // BC_ENABLED *n = bc_program_num(p, *r); @@ -286,7 +286,7 @@ static void bc_program_binPrep(BcProgram *p, BcResult **l, BcNum **ln, #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); + bc_vm_err(BC_ERROR_EXEC_STACK); } #endif // BC_PROG_NO_STACK_CHECK @@ -306,7 +306,7 @@ static void bc_program_binPrep(BcProgram *p, BcResult **l, BcNum **ln, 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); + if (BC_ERR(lt == BC_RESULT_STR)) bc_vm_err(BC_ERROR_EXEC_TYPE); } static void bc_program_binOpPrep(BcProgram *p, BcResult **l, BcNum **ln, @@ -329,7 +329,7 @@ static void bc_program_assignPrep(BcProgram *p, BcResult **l, BcNum **ln, lt = (*l)->t; if (BC_ERR(lt >= min && lt <= BC_RESULT_ONE)) - bc_vm_err(BC_ERR_EXEC_TYPE); + bc_vm_err(BC_ERROR_EXEC_TYPE); #if DC_ENABLED if(BC_IS_DC) { @@ -351,7 +351,7 @@ static void bc_program_prep(BcProgram *p, BcResult **r, BcNum **n, size_t idx) { #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); + bc_vm_err(BC_ERROR_EXEC_STACK); } #endif // BC_PROG_NO_STACK_CHECK @@ -391,7 +391,7 @@ static void bc_program_const(BcProgram *p, const char *code, size_t *bgn) { } // bc_num_parse() should only do operations that cannot fail. - bc_num_parse(&c->num, c->val, base); + bc_num_parse(&c->num, c->val, base, !c->val[1]); c->base = base; } @@ -419,9 +419,6 @@ static void bc_program_op(BcProgram *p, uchar inst) { 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); @@ -440,7 +437,7 @@ static void bc_program_read(BcProgram *p) { 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_vm_err(BC_ERROR_EXEC_REC_READ); } BC_SIG_LOCK; @@ -457,13 +454,13 @@ static void bc_program_read(BcProgram *p) { bc_vec_npop(&f->code, f->code.len); s = bc_read_line(&buf, BC_IS_BC ? "read> " : "?> "); - if (s == BC_STATUS_EOF) bc_vm_err(BC_ERR_EXEC_READ_EXPR); + if (s == BC_STATUS_EOF) bc_vm_err(BC_ERROR_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); + bc_vm_err(BC_ERROR_EXEC_READ_EXPR); #if BC_ENABLED if (BC_G) bc_program_prepGlobals(p); @@ -498,12 +495,6 @@ exec_err: 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 @@ -569,7 +560,7 @@ static void bc_program_print(BcProgram *p, uchar inst, size_t idx) { #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); + bc_vm_err(BC_ERROR_EXEC_STACK); } #endif // BC_PROG_NO_STACK_CHECK @@ -579,7 +570,7 @@ static void bc_program_print(BcProgram *p, uchar inst, size_t idx) { #if BC_ENABLED if (r->t == BC_RESULT_VOID) { - if (BC_ERR(pop)) bc_vm_err(BC_ERR_EXEC_VOID_VAL); + if (BC_ERR(pop)) bc_vm_err(BC_ERROR_EXEC_VOID_VAL); bc_vec_pop(&p->results); return; } @@ -613,7 +604,7 @@ static void bc_program_print(BcProgram *p, uchar inst, size_t idx) { 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); + if (BC_NUM_NONZERO(&r->d.n)) r->d.n.neg = !r->d.n.neg; } void bc_program_not(BcResult *r, BcNum *n) { @@ -752,7 +743,7 @@ static void bc_program_copyToVar(BcProgram *p, size_t idx, if (BC_IS_DC) { if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) - bc_vm_err(BC_ERR_EXEC_STACK); + bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 1)); @@ -777,7 +768,7 @@ static void bc_program_copyToVar(BcProgram *p, size_t idx, #if DC_ENABLED if (BC_IS_DC && (ptr->t == BC_RESULT_STR || BC_PROG_STR(n))) { - if (BC_ERR(!var)) bc_vm_err(BC_ERR_EXEC_TYPE); + if (BC_ERR(!var)) bc_vm_err(BC_ERROR_EXEC_TYPE); bc_program_assignStr(p, ptr, vec, true); return; } @@ -880,9 +871,6 @@ static void bc_program_assign(BcProgram *p, uchar inst) { 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 @@ -894,10 +882,10 @@ static void bc_program_assign(BcProgram *p, uchar inst) { BcVec *v; BcBigDig *ptr, *ptr_t, val, max, min; - BcErr e; + BcError e; bc_num_bigdig(l, &val); - e = left->t - BC_RESULT_IBASE + BC_ERR_EXEC_IBASE; + e = left->t - BC_RESULT_IBASE + BC_ERROR_EXEC_IBASE; if (sc) { min = 0; @@ -952,7 +940,7 @@ static void bc_program_pushVar(BcProgram *p, const char *restrict code, 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); + if (BC_ERR(!BC_PROG_STACK(v, 2 - copy))) bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(v, 2 - copy)); @@ -1070,9 +1058,9 @@ static void bc_program_call(BcProgram *p, const char *restrict code, 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(!f->code.len)) bc_vm_verr(BC_ERROR_EXEC_UNDEF_FUNC, f->name); if (BC_ERR(nparams != f->nparams)) - bc_vm_verr(BC_ERR_EXEC_PARAMS, f->nparams, nparams); + bc_vm_verr(BC_ERROR_EXEC_PARAMS, f->nparams, nparams); ip.len = p->results.len - nparams; assert(BC_PROG_STACK(&p->results, nparams)); @@ -1085,7 +1073,8 @@ static void bc_program_call(BcProgram *p, const char *restrict code, 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); + if (BC_ERR(arg->t == BC_RESULT_VOID)) + bc_vm_err(BC_ERROR_EXEC_VOID_VAL); a = bc_vec_item(&f->autos, nparams - 1 - i); @@ -1189,7 +1178,7 @@ static void bc_program_builtin(BcProgram *p, uchar inst) { #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); + bc_vm_err(BC_ERROR_EXEC_STACK); } #endif // BC_PROG_NO_STACK_CHECK @@ -1214,7 +1203,7 @@ static void bc_program_builtin(BcProgram *p, uchar inst) { BC_SIG_UNLOCK; - BC_NUM_NEG_CLR_NP(res->d.n); + res->d.n.neg = false; } #if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND else if (inst == BC_INST_IRAND) { @@ -1282,7 +1271,7 @@ static void bc_program_divmod(BcProgram *p) { BcNum *n1, *n2; size_t req; - bc_vec_grow(&p->results, 2); + bc_vec_expand(&p->results, p->results.len + 2); // We don't need to update the pointer because // the capacity is enough due to the line above. @@ -1310,7 +1299,7 @@ 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); + if (BC_ERR(!BC_PROG_STACK(&p->results, 3))) bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 3)); @@ -1357,7 +1346,7 @@ static uchar bc_program_asciifyNum(BcProgram *p, BcNum *n) { BC_SIG_UNLOCK; bc_num_truncate(&num, num.scale); - BC_NUM_NEG_CLR_NP(num); + num.neg = false; // This is guaranteed to not have a divide by 0 // because strmb is equal to UCHAR_MAX + 1. @@ -1383,7 +1372,7 @@ static void bc_program_asciify(BcProgram *p) { uchar c; size_t idx; - if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERR_EXEC_STACK); + if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 1)); @@ -1420,7 +1409,7 @@ 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); + if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 1)); @@ -1482,7 +1471,7 @@ static void bc_program_execStr(BcProgram *p, const char *restrict code, assert(p->stack.len == p->tail_calls.len); - if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERR_EXEC_STACK); + if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 1)); @@ -1507,7 +1496,7 @@ static void bc_program_execStr(BcProgram *p, const char *restrict code, 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); + if (BC_ERR(!BC_PROG_STR(n))) bc_vm_err(BC_ERROR_EXEC_TYPE); BC_UNSETJMP; BC_SIG_UNLOCK; @@ -1843,8 +1832,6 @@ void bc_program_exec(BcProgram *p) { bc_vec_pop(&p->results); } // Fallthrough. - BC_FALLTHROUGH - case BC_INST_JUMP: { idx = bc_program_index(code, &ip->idx); @@ -2090,7 +2077,7 @@ void bc_program_exec(BcProgram *p) { #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); + bc_vm_err(BC_ERROR_EXEC_STACK); } #endif // BC_PROG_NO_STACK_CHECK @@ -2158,7 +2145,7 @@ void bc_program_exec(BcProgram *p) { case BC_INST_DUPLICATE: { if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) - bc_vm_err(BC_ERR_EXEC_STACK); + bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 1)); @@ -2179,7 +2166,7 @@ void bc_program_exec(BcProgram *p) { BcResult *ptr2; if (BC_ERR(!BC_PROG_STACK(&p->results, 2))) - bc_vm_err(BC_ERR_EXEC_STACK); + bc_vm_err(BC_ERROR_EXEC_STACK); assert(BC_PROG_STACK(&p->results, 2)); diff --git a/src/read.c b/src/read.c index 45e868c927da..6886a7e13602 100644 --- a/src/read.c +++ b/src/read.c @@ -143,7 +143,7 @@ BcStatus bc_read_chars(BcVec *vec, const char *prompt) { BC_SIG_UNLOCK; - bc_vm_err(BC_ERR_FATAL_IO_ERR); + bc_vm_err(BC_ERROR_FATAL_IO_ERR); } BC_SIG_UNLOCK; @@ -177,14 +177,14 @@ BcStatus bc_read_line(BcVec *vec, const char *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); + bc_vm_verr(BC_ERROR_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; + BcError e = BC_ERROR_FATAL_IO_ERR; size_t size, r; struct stat pstat; int fd; @@ -194,11 +194,11 @@ void bc_read_file(const char *path, char **buf) { assert(path != NULL); fd = open(path, O_RDONLY); - if (BC_ERR(fd < 0)) bc_vm_verr(BC_ERR_FATAL_FILE_ERR, path); + if (BC_ERR(fd < 0)) bc_vm_verr(BC_ERROR_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; + e = BC_ERROR_FATAL_PATH_DIR; goto malloc_err; } @@ -211,7 +211,7 @@ void bc_read_file(const char *path, char **buf) { (*buf)[size] = '\0'; if (BC_ERR(bc_read_binary(*buf, size))) { - e = BC_ERR_FATAL_BIN_FILE; + e = BC_ERROR_FATAL_BIN_FILE; goto read_err; } diff --git a/src/vector.c b/src/vector.c index df6936aaeb76..f45bcb198a25 100644 --- a/src/vector.c +++ b/src/vector.c @@ -37,11 +37,12 @@ #include <stdlib.h> #include <string.h> +#include <status.h> #include <vector.h> #include <lang.h> #include <vm.h> -void bc_vec_grow(BcVec *restrict v, size_t n) { +static void bc_vec_grow(BcVec *restrict v, size_t n) { size_t len, cap = v->cap; sig_atomic_t lock; @@ -56,15 +56,13 @@ #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 @@ -86,14 +84,12 @@ BC_NORETURN void bc_vm_jmp(void) { 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. @@ -136,28 +132,8 @@ void bc_vm_info(const char* const help) { bc_file_flush(&vm.fout); } -#endif // !BC_ENABLE_LIBRARY - -#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, ...) { +void bc_vm_error(BcError e, size_t line, ...) { BcStatus s; va_list args; @@ -165,11 +141,11 @@ void bc_vm_handleError(BcErr e, size_t line, ...) { const char* err_type = vm.err_ids[id]; sig_atomic_t lock; - assert(e < BC_ERR_NELEMS); + assert(e < BC_ERROR_NELEMS); assert(!vm.sig_pop); #if BC_ENABLED - if (!BC_S && e >= BC_ERR_POSIX_START) { + if (!BC_S && e >= BC_ERROR_POSIX_START) { if (BC_W) { // Make sure to not return an error. id = UCHAR_MAX; @@ -285,7 +261,7 @@ static void bc_vm_envArgs(const char* const env_args_name) { buf += 1; start = buf; } - else if (instr) bc_vm_error(BC_ERR_FATAL_OPTION, 0, start); + else if (instr) bc_vm_error(BC_ERROR_FATAL_OPTION, 0, start); } else buf += 1; } @@ -317,7 +293,6 @@ static size_t bc_vm_envLen(const char *var) { return len; } -#endif // BC_ENABLE_LIBRARY void bc_vm_shutdown(void) { @@ -333,7 +308,6 @@ void bc_vm_shutdown(void) { #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); @@ -341,40 +315,31 @@ void bc_vm_shutdown(void) { bc_program_free(&vm.prog); bc_parse_free(&vm.prs); -#endif // !BC_ENABLE_LIBRARY - bc_vm_freeTemps(); - bc_vec_free(&vm.temps); + { + size_t i; + for (i = 0; i < vm.temps.len; ++i) + free(((BcNum*) bc_vec_item(&vm.temps, i))->num); + + 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_err(BC_ERR_FATAL_ALLOC_ERR); + bc_vm_err(BC_ERROR_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_err(BC_ERR_FATAL_ALLOC_ERR); + bc_vm_err(BC_ERROR_FATAL_ALLOC_ERR); return res; } @@ -386,7 +351,7 @@ void* bc_vm_malloc(size_t n) { ptr = malloc(n); - if (BC_ERR(ptr == NULL)) bc_vm_err(BC_ERR_FATAL_ALLOC_ERR); + if (BC_ERR(ptr == NULL)) bc_vm_err(BC_ERROR_FATAL_ALLOC_ERR); return ptr; } @@ -399,7 +364,7 @@ void* bc_vm_realloc(void *ptr, size_t n) { temp = realloc(ptr, n); - if (BC_ERR(temp == NULL)) bc_vm_err(BC_ERR_FATAL_ALLOC_ERR); + if (BC_ERR(temp == NULL)) bc_vm_err(BC_ERROR_FATAL_ALLOC_ERR); return temp; } @@ -412,12 +377,11 @@ char* bc_vm_strdup(const char *str) { s = strdup(str); - if (BC_ERR(!s)) bc_vm_err(BC_ERR_FATAL_ALLOC_ERR); + if (BC_ERR(!s)) bc_vm_err(BC_ERROR_FATAL_ALLOC_ERR); return s; } -#if !BC_ENABLE_LIBRARY void bc_vm_printf(const char *fmt, ...) { va_list args; @@ -432,18 +396,12 @@ void bc_vm_printf(const char *fmt, ...) { BC_SIG_UNLOCK; } -#endif // !BC_ENABLE_LIBRARY void bc_vm_putchar(int c) { -#if BC_ENABLE_LIBRARY - bc_vec_pushByte(&vm.out, (uchar) c); -#else // BC_ENABLE_LIBRARY bc_file_putchar(&vm.fout, (uchar) c); vm.nchars = (c == '\n' ? 0 : vm.nchars + 1); -#endif // BC_ENABLE_LIBRARY } -#if !BC_ENABLE_LIBRARY static void bc_vm_clean(void) { BcVec *fns = &vm.prog.fns; @@ -533,7 +491,7 @@ static void bc_vm_endif(void) { if (good) { while (BC_PARSE_IF_END(&vm.prs)) bc_vm_process("else {}"); } - else bc_parse_err(&vm.prs, BC_ERR_PARSE_BLOCK); + else bc_parse_err(&vm.prs, BC_ERROR_PARSE_BLOCK); } #endif // BC_ENABLED @@ -646,9 +604,9 @@ restart: if (!BC_STATUS_IS_ERROR(s)) { if (BC_ERR(comment)) - bc_parse_err(&vm.prs, BC_ERR_PARSE_COMMENT); + bc_parse_err(&vm.prs, BC_ERROR_PARSE_COMMENT); else if (BC_ERR(string)) - bc_parse_err(&vm.prs, BC_ERR_PARSE_STRING); + bc_parse_err(&vm.prs, BC_ERROR_PARSE_STRING); #if BC_ENABLED else if (BC_IS_BC) bc_vm_endif(); #endif // BC_ENABLED @@ -694,7 +652,7 @@ static void bc_vm_defaultMsgs(void) { 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]; + for (i = 0; i < BC_ERROR_NELEMS; ++i) vm.err_msgs[i] = bc_err_msgs[i]; } static void bc_vm_gettext(void) { @@ -725,7 +683,7 @@ static void bc_vm_gettext(void) { i = 0; id = bc_err_ids[i]; - for (set = id + 3, msg = 1; i < BC_ERR_NELEMS; ++i, ++msg) { + for (set = id + 3, msg = 1; i < BC_ERROR_NELEMS; ++i, ++msg) { if (id != bc_err_ids[i]) { msg = 1; @@ -817,8 +775,8 @@ err: #endif // NDEBUG } -void bc_vm_boot(int argc, char *argv[], const char *env_len, - const char* const env_args) +void bc_vm_boot(int argc, char *argv[], const char *env_len, + const char* const env_args) { int ttyin, ttyout, ttyerr; struct sigaction sa; @@ -845,7 +803,10 @@ void bc_vm_boot(int argc, char *argv[], const char *env_len, if (BC_TTY) sigaction(SIGHUP, &sa, NULL); #endif // BC_ENABLE_HISTORY - bc_vm_init(); + memcpy(vm.max_num, bc_num_bigdigMax, + bc_num_bigdigMax_size * sizeof(BcDig)); + bc_num_setup(&vm.max, vm.max_num, BC_NUM_BIGDIG_LOG10); + vm.max.len = bc_num_bigdigMax_size; vm.file = NULL; @@ -861,6 +822,8 @@ void bc_vm_boot(int argc, char *argv[], const char *env_len, bc_vec_clear(&vm.files); bc_vec_clear(&vm.exprs); + bc_vec_init(&vm.temps, sizeof(BcNum), NULL); + bc_program_init(&vm.prog); bc_parse_init(&vm.prs, &vm.prog, BC_PROG_MAIN); @@ -879,27 +842,6 @@ void bc_vm_boot(int argc, char *argv[], const char *env_len, 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; @@ -909,11 +851,11 @@ void bc_vm_init(void) { #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 + + BC_SIG_UNLOCK; + + bc_vm_exec(); } |