Vendor import of Gavin Howard's bc-3.3.0
This commit is contained in:
parent
47a52dc4d4
commit
f131090388
@ -29,7 +29,7 @@
|
||||
#
|
||||
.POSIX:
|
||||
|
||||
VERSION = 3.2.6
|
||||
VERSION = 3.3.0
|
||||
|
||||
SRC = %%SRC%%
|
||||
OBJ = %%OBJ%%
|
||||
|
20
NEWS.md
20
NEWS.md
@ -1,5 +1,25 @@
|
||||
# News
|
||||
|
||||
## 3.3.0
|
||||
|
||||
This is a production release that changes one behavior and fixes documentation
|
||||
bugs.
|
||||
|
||||
The changed behavior is the treatment of `-e` and `-f` when given through
|
||||
`BC_ENV_ARGS` or `DC_ENV_ARGS`. Now `bc` and `dc` do not exit when those options
|
||||
(or their equivalents) are given through those environment variables. However,
|
||||
`bc` and `dc` still exit when they or their equivalents are given on the
|
||||
command-line.
|
||||
|
||||
## 3.2.7
|
||||
|
||||
This is a production release that removes a small non-portable shell operation
|
||||
in `configure.sh`. This problem was only noticed on OpenBSD, not FreeBSD or
|
||||
Linux.
|
||||
|
||||
Non-OpenBSD users do ***NOT*** need to upgrade, although NetBSD users may also
|
||||
need to upgrade.
|
||||
|
||||
## 3.2.6
|
||||
|
||||
This is a production release that fixes the build on FreeBSD.
|
||||
|
@ -342,7 +342,7 @@ Folders:
|
||||
[20]: https://git.yzena.com/gavin/bc
|
||||
[21]: https://gavinhoward.com/2020/04/i-am-moving-away-from-github/
|
||||
[22]: https://www.deepl.com/translator
|
||||
[23]: https://svnweb.freebsd.org/base/head/contrib/bc/
|
||||
[23]: https://cgit.freebsd.org/src/tree/contrib/bc
|
||||
[24]: https://bugs.freebsd.org/
|
||||
[25]: https://reviews.freebsd.org/
|
||||
[26]: ./manuals/bcl.3.md
|
||||
|
@ -253,7 +253,7 @@ replace_ext() {
|
||||
_replace_ext_ext1="$2"
|
||||
_replace_ext_ext2="$3"
|
||||
|
||||
_replace_ext_result=${_replace_ext_file%.$_replace_ext_ext1}.$_replace_ext_ext2
|
||||
_replace_ext_result="${_replace_ext_file%.$_replace_ext_ext1}.$_replace_ext_ext2"
|
||||
|
||||
printf '%s\n' "$_replace_ext_result"
|
||||
}
|
||||
@ -1199,17 +1199,12 @@ SRC_TARGETS=""
|
||||
|
||||
src_files=$(find_src_files $unneeded)
|
||||
|
||||
temp_ifs="$IFS"
|
||||
IFS=$'\n'
|
||||
|
||||
for f in $src_files; do
|
||||
o=$(replace_ext "$f" "c" "o")
|
||||
SRC_TARGETS=$(printf '%s\n\n%s: %s %s\n\t$(CC) $(CFLAGS) -o %s -c %s\n' \
|
||||
"$SRC_TARGETS" "$o" "$headers" "$f" "$o" "$f")
|
||||
done
|
||||
|
||||
IFS="$temp_ifs"
|
||||
|
||||
contents=$(replace "$contents" "HEADERS" "$headers")
|
||||
|
||||
contents=$(replace "$contents" "BC_ENABLED" "$bc")
|
||||
|
@ -39,7 +39,7 @@
|
||||
#include <status.h>
|
||||
#include <vm.h>
|
||||
|
||||
void bc_args(int argc, char *argv[]);
|
||||
void bc_args(int argc, char *argv[], bool exit_exprs);
|
||||
|
||||
extern const char* const bc_args_env_name;
|
||||
|
||||
|
@ -176,11 +176,15 @@ typedef enum BcErr {
|
||||
#endif // __STDC_VERSION__
|
||||
|
||||
#if defined(__clang__) || defined(__GNUC__)
|
||||
#if defined(__has_attribute) && __has_attribute(fallthrough)
|
||||
#if defined(__has_attribute)
|
||||
#if __has_attribute(fallthrough)
|
||||
#define BC_FALLTHROUGH __attribute__((fallthrough));
|
||||
#else // defined(__has_attribute) && __has_attribute(fallthrough)
|
||||
#else // __has_attribute(fallthrough)
|
||||
#define BC_FALLTHROUGH
|
||||
#endif // defined(__has_attribute) && __has_attribute(fallthrough)
|
||||
#endif // __has_attribute(fallthrough)
|
||||
#else // defined(__has_attribute)
|
||||
#define BC_FALLTHROUGH
|
||||
#endif // defined(__has_attribute)
|
||||
#else // defined(__clang__) || defined(__GNUC__)
|
||||
#define BC_FALLTHROUGH
|
||||
#endif // defined(__clang__) || defined(__GNUC__)
|
||||
|
@ -356,6 +356,7 @@ typedef struct BcVm {
|
||||
uint16_t line_len;
|
||||
|
||||
bool no_exit_exprs;
|
||||
bool exit_exprs;
|
||||
bool eof;
|
||||
#endif // !BC_ENABLE_LIBRARY
|
||||
|
||||
|
@ -229,10 +229,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -242,8 +245,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -251,7 +258,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -230,12 +230,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -247,9 +251,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -258,6 +268,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -187,10 +187,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -200,8 +203,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -209,7 +216,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -192,12 +192,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -209,9 +213,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -220,6 +230,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -171,10 +171,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -184,8 +187,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -193,7 +200,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -189,12 +189,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -206,9 +210,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -217,6 +227,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -168,10 +168,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -181,8 +184,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -190,7 +197,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -189,12 +189,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -206,9 +210,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -217,6 +227,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -168,10 +168,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -181,8 +184,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -190,7 +197,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -184,12 +184,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -201,9 +205,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -212,6 +222,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -164,10 +164,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -177,8 +180,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -186,7 +193,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -184,12 +184,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -201,9 +205,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -212,6 +222,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -164,10 +164,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -177,8 +180,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -186,7 +193,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -192,12 +192,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -209,9 +213,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -220,6 +230,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -171,10 +171,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -184,8 +187,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -193,7 +200,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -187,12 +187,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -204,9 +208,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -215,6 +225,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -167,10 +167,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -180,8 +183,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -189,7 +196,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -187,12 +187,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -204,9 +208,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -215,6 +225,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -167,10 +167,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -180,8 +183,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -189,7 +196,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -225,12 +225,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -242,9 +246,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -253,6 +263,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -183,10 +183,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -196,8 +199,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -205,7 +212,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -225,12 +225,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -242,9 +246,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -253,6 +263,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -183,10 +183,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -196,8 +199,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -205,7 +212,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -220,12 +220,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -237,9 +241,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -248,6 +258,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -179,10 +179,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -192,8 +195,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -201,7 +208,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -220,12 +220,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -237,9 +241,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -248,6 +258,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -179,10 +179,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -192,8 +195,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -201,7 +208,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -230,12 +230,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -247,9 +251,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -258,6 +268,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -187,10 +187,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -200,8 +203,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -209,7 +216,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -225,12 +225,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -242,9 +246,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -253,6 +263,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -183,10 +183,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -196,8 +199,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -205,7 +212,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bc - arbitrary-precision decimal arithmetic language and calculator
|
||||
@ -225,12 +225,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, bc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]BC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[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[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -242,9 +246,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, bc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, bc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -253,6 +263,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
|
@ -183,10 +183,13 @@ The following are the options that bc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **BC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -196,8 +199,12 @@ The following are the options that bc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, bc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **BC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, bc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, bc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -205,7 +212,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other bc(1) implementations, this bc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "BCL" "3" "January 2021" "Gavin D. Howard" "Libraries Manual"
|
||||
.TH "BCL" "3" "February 2021" "Gavin D. Howard" "Libraries Manual"
|
||||
.SH NAME
|
||||
.PP
|
||||
bcl - library of arbitrary precision decimal arithmetic
|
||||
|
@ -164,6 +164,22 @@ Can be overridden by passing the `--bindir` option to `configure.sh`.
|
||||
|
||||
Defaults to `$PREFIX/bin`.
|
||||
|
||||
### `INCLUDEDIR`
|
||||
|
||||
The directory to install header files in.
|
||||
|
||||
Can be overridden by passing the `--includedir` option to `configure.sh`.
|
||||
|
||||
Defaults to `$PREFIX/include`.
|
||||
|
||||
### `LIBDIR`
|
||||
|
||||
The directory to install libraries in.
|
||||
|
||||
Can be overridden by passing the `--libdir` option to `configure.sh`.
|
||||
|
||||
Defaults to `$PREFIX/lib`.
|
||||
|
||||
### `DATAROOTDIR`
|
||||
|
||||
The root directory to install data files in.
|
||||
|
@ -106,8 +106,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -117,10 +122,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -128,7 +135,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -209,7 +218,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1073,7 +1082,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -235,7 +248,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1164,7 +1177,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -198,7 +207,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1033,7 +1042,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -959,7 +972,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -868,7 +877,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -959,7 +972,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -868,7 +877,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -959,7 +972,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -868,7 +877,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -954,7 +967,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -865,7 +874,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -954,7 +967,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -865,7 +874,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -959,7 +972,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -868,7 +877,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -954,7 +967,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -865,7 +874,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -954,7 +967,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -865,7 +874,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -235,7 +248,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1164,7 +1177,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -198,7 +207,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1033,7 +1042,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -235,7 +248,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1164,7 +1177,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -198,7 +207,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1033,7 +1042,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -230,7 +243,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1159,7 +1172,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -195,7 +204,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1030,7 +1039,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -230,7 +243,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1159,7 +1172,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -195,7 +204,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1030,7 +1039,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -116,9 +116,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -130,12 +137,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -144,6 +154,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -235,7 +248,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1164,7 +1177,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -101,8 +101,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -112,10 +117,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -123,7 +130,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -198,7 +207,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1033,7 +1042,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -230,7 +243,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1159,7 +1172,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -195,7 +204,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1030,7 +1039,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -25,7 +25,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.SH Name
|
||||
.PP
|
||||
dc - arbitrary-precision decimal reverse-Polish notation calculator
|
||||
@ -111,9 +111,16 @@ This means that if a file is given before an expression, the file is
|
||||
read in and evaluated first.
|
||||
.RS
|
||||
.PP
|
||||
After processing all expressions and files, dc(1) will exit, unless
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
|
||||
\f[B]DC_ENV_ARGS\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -125,12 +132,15 @@ 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
|
||||
If this option is given on the command-line (i.e., not in
|
||||
\f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
|
||||
then after processing all expressions and files, dc(1) will exit, unless
|
||||
\f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
|
||||
\f[B]-f\f[R] or \f[B]\[en]file\f[R].
|
||||
However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after that,
|
||||
bc(1) will give a fatal error and exit.
|
||||
\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
|
||||
\f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
|
||||
exit.
|
||||
.PP
|
||||
This is a \f[B]non-portable extension\f[R].
|
||||
.RE
|
||||
@ -139,6 +149,9 @@ All long options are \f[B]non-portable extensions\f[R].
|
||||
.SH STDOUT
|
||||
.PP
|
||||
Any non-error output is written to \f[B]stdout\f[R].
|
||||
In addition, if history (see the \f[B]HISTORY\f[R] section) and the
|
||||
prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
|
||||
to \f[B]stdout\f[R].
|
||||
.PP
|
||||
\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
|
||||
issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
|
||||
@ -230,7 +243,7 @@ guaranteed to \f[B]NOT\f[R] be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator.
|
||||
However, they \f[I]are\f[R] guaranteed to be reproducible with identical
|
||||
\f[B]seed\f[R] values.
|
||||
This means that the pseudo-random values from bc(1) should only be used
|
||||
This means that the pseudo-random values from dc(1) should only be used
|
||||
where a reproducible stream of pseudo-random numbers is
|
||||
\f[I]ESSENTIAL\f[R].
|
||||
In any other case, use a non-seeded pseudo-random number generator.
|
||||
@ -1159,7 +1172,7 @@ will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
|
||||
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
|
||||
in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
|
||||
file with double quotes.
|
||||
However, handling a file with both kinds of quotes in
|
||||
\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
|
||||
|
@ -98,8 +98,13 @@ The following are the options that dc(1) accepts.
|
||||
evaluated in the order given. This means that if a file is given before an
|
||||
expression, the file is read in and evaluated first.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**, whether on the
|
||||
command-line or in **DC_ENV_ARGS**. However, if any other **-e**,
|
||||
**--expression**, **-f**, or **--file** arguments are given after **-f-** or
|
||||
equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -109,10 +114,12 @@ The following are the options that dc(1) accepts.
|
||||
through **stdin**. If expressions are also given (see above), the
|
||||
expressions are evaluated in the order given.
|
||||
|
||||
After processing all expressions and files, dc(1) will exit, unless **-**
|
||||
(**stdin**) was given as an argument at least once to **-f** or **--file**.
|
||||
However, if any other **-e**, **--expression**, **-f**, or **--file**
|
||||
arguments are given after that, bc(1) will give a fatal error and exit.
|
||||
If this option is given on the command-line (i.e., not in **DC_ENV_ARGS**,
|
||||
see the **ENVIRONMENT VARIABLES** section), then after processing all
|
||||
expressions and files, dc(1) will exit, unless **-** (**stdin**) was given
|
||||
as an argument at least once to **-f** or **--file**. However, if any other
|
||||
**-e**, **--expression**, **-f**, or **--file** arguments are given after
|
||||
**-f-** or equivalent is given, dc(1) will give a fatal error and exit.
|
||||
|
||||
This is a **non-portable extension**.
|
||||
|
||||
@ -120,7 +127,9 @@ All long options are **non-portable extensions**.
|
||||
|
||||
# STDOUT
|
||||
|
||||
Any non-error output is written to **stdout**.
|
||||
Any non-error output is written to **stdout**. In addition, if history (see the
|
||||
**HISTORY** section) and the prompt (see the **TTY MODE** section) are enabled,
|
||||
both are output to **stdout**.
|
||||
|
||||
**Note**: Unlike other dc(1) implementations, this dc(1) will issue a fatal
|
||||
error (see the **EXIT STATUS** section) if it cannot write to **stdout**, so if
|
||||
@ -195,7 +204,7 @@ command or the **"** command that does not get receive a value of **0** or
|
||||
**'** and **"** commands are guaranteed to **NOT** be cryptographically secure.
|
||||
This is a consequence of using a seeded pseudo-random number generator. However,
|
||||
they *are* guaranteed to be reproducible with identical **seed** values. This
|
||||
means that the pseudo-random values from bc(1) should only be used where a
|
||||
means that the pseudo-random values from dc(1) should only be used where a
|
||||
reproducible stream of pseudo-random numbers is *ESSENTIAL*. In any other case,
|
||||
use a non-seeded pseudo-random number generator.
|
||||
|
||||
@ -1030,7 +1039,7 @@ dc(1) recognizes the following environment variables:
|
||||
|
||||
The quote parsing will handle either kind of quotes, **'** or **"**. Thus,
|
||||
if you have a file with any number of single quotes in the name, you can use
|
||||
double quotes as the outside quotes, as in **"some 'bc' file.bc"**, and vice
|
||||
double quotes as the outside quotes, as in **"some 'dc' file.dc"**, and vice
|
||||
versa if you have a file with double quotes. However, handling a file with
|
||||
both kinds of quotes in **DC_ENV_ARGS** is not supported due to the
|
||||
complexity of the parsing, though such files are still supported on the
|
||||
|
@ -1 +1 @@
|
||||
.TH "BC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "BC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
|
@ -1 +1 @@
|
||||
.TH "BCL" "3" "January 2021" "Gavin D. Howard" "Libraries Manual"
|
||||
.TH "BCL" "3" "February 2021" "Gavin D. Howard" "Libraries Manual"
|
||||
|
@ -1 +1 @@
|
||||
.TH "DC" "1" "January 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
|
||||
|
@ -575,7 +575,7 @@ if [ "$run_tests" -ne 0 ]; then
|
||||
printf '\n'
|
||||
printf ' <github_release> %s release.sh RELEASE.md\\\n' "$version"
|
||||
printf ' tests/afl.py tests/radamsa.sh tests/radamsa.txt tests/randmath.py \\\n'
|
||||
printf ' tests/bc/scripts/timeconst.bc\n'
|
||||
printf ' tests/fuzzing/ tests/bc/scripts/timeconst.bc\n'
|
||||
|
||||
fi
|
||||
|
||||
|
@ -89,7 +89,7 @@ static void bc_args_file(const char *file) {
|
||||
free(buf);
|
||||
}
|
||||
|
||||
void bc_args(int argc, char *argv[]) {
|
||||
void bc_args(int argc, char *argv[], bool exit_exprs) {
|
||||
|
||||
int c;
|
||||
size_t i;
|
||||
@ -109,6 +109,7 @@ void bc_args(int argc, char *argv[]) {
|
||||
if (vm.no_exit_exprs)
|
||||
bc_vm_verr(BC_ERR_FATAL_OPTION, "-e (--expression)");
|
||||
bc_args_exprs(opts.optarg);
|
||||
vm.exit_exprs = (exit_exprs || vm.exit_exprs);
|
||||
break;
|
||||
}
|
||||
|
||||
@ -119,6 +120,7 @@ void bc_args(int argc, char *argv[]) {
|
||||
if (vm.no_exit_exprs)
|
||||
bc_vm_verr(BC_ERR_FATAL_OPTION, "-f (--file)");
|
||||
bc_args_file(opts.optarg);
|
||||
vm.exit_exprs = (exit_exprs || vm.exit_exprs);
|
||||
}
|
||||
break;
|
||||
}
|
||||
|
6
src/vm.c
6
src/vm.c
@ -315,7 +315,7 @@ static void bc_vm_envArgs(const char* const env_args_name) {
|
||||
buf = NULL;
|
||||
bc_vec_push(&vm.env_args, &buf);
|
||||
|
||||
bc_args((int) vm.env_args.len - 1, bc_vec_item(&vm.env_args, 0));
|
||||
bc_args((int) vm.env_args.len - 1, bc_vec_item(&vm.env_args, 0), false);
|
||||
}
|
||||
|
||||
static size_t bc_vm_envLen(const char *var) {
|
||||
@ -820,7 +820,7 @@ static void bc_vm_exec(void) {
|
||||
|
||||
BC_SIG_UNLOCK;
|
||||
|
||||
if (!vm.no_exit_exprs) return;
|
||||
if (!vm.no_exit_exprs && vm.exit_exprs) return;
|
||||
}
|
||||
|
||||
for (i = 0; i < vm.files.len; ++i) {
|
||||
@ -905,7 +905,7 @@ void bc_vm_boot(int argc, char *argv[], const char *env_len,
|
||||
#endif // BC_ENABLED
|
||||
|
||||
bc_vm_envArgs(env_args);
|
||||
bc_args(argc, argv);
|
||||
bc_args(argc, argv, true);
|
||||
|
||||
#if BC_ENABLED
|
||||
if (BC_IS_POSIX) vm.flags &= ~(BC_FLAG_G);
|
||||
|
@ -141,7 +141,7 @@ if [ -f "$orig" ]; then
|
||||
elif [ -f "$results" ]; then
|
||||
res="$results"
|
||||
elif [ "$generate" -eq 0 ]; then
|
||||
printf 'Skipping %s script %s\n' "$d" "$s"
|
||||
printf 'Skipping %s script %s\n' "$d" "$f"
|
||||
exit 0
|
||||
else
|
||||
printf 'Generating %s results...' "$f"
|
||||
|
Loading…
Reference in New Issue
Block a user