Lines Matching full:dc
28 .TH "DC" "1" "August 2024" "Gavin D. Howard" "General Commands Manual"
34 \f[B]dc\f[R] [\f[B]\-cChiPRvVx\f[R]] [\f[B]\-\-version\f[R]]
50 If no files are given on the command\-line, then dc(1) reads from
52 Otherwise, those files are processed, and dc(1) will then exit.
58 and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
60 The following are the options that dc(1) accepts.
114 then after processing all expressions and files, dc(1) will exit, unless
120 \f[B]\-f\-\f[R] or equivalent is given, dc(1) will give a fatal error
135 then after processing all expressions and files, dc(1) will exit, unless
140 \f[B]\-f\-\f[R] or equivalent is given, dc(1) will give a fatal error
194 to having them in dc(1).
210 used to having them in dc(1).
213 This option is also useful in hash bang lines of dc(1) scripts that
251 Makes dc(1) print all numbers greater than \f[B]\-1\f[R] and less than
262 \f[B]\-\-expression\f[R] options, then dc(1) reads from \f[B]stdin\f[R].
270 balanced before dc(1) parses and executes.
277 \f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
280 \f[B]dc >&\-\f[R], it will quit with an error.
281 This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
284 If there are scripts that depend on the behavior of other dc(1)
290 \f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
293 \f[B]dc 2>&\-\f[R], it will quit with an error.
294 This is done so that dc(1) can exit with an error code when
297 If there are scripts that depend on the behavior of other dc(1)
313 The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
332 The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
783 If either or both of the values are not numbers, dc(1) will raise an
792 If either or both of the values are not numbers, dc(1) will raise an
804 If either or both of the values are not numbers, dc(1) will raise an
813 If either or both of the values are not numbers, dc(1) will raise an
825 If either or both of the values are not numbers, dc(1) will raise an
834 If either or both of the values are not numbers, dc(1) will raise an
846 If either or both of the values are not numbers, dc(1) will raise an
855 If either or both of the values are not numbers, dc(1) will raise an
867 If either or both of the values are not numbers, dc(1) will raise an
876 If either or both of the values are not numbers, dc(1) will raise an
888 If either or both of the values are not numbers, dc(1) will raise an
897 If either or both of the values are not numbers, dc(1) will raise an
910 If there are no macros, or only one macro executing, dc(1) exits.
916 macros, dc(1) exits.
922 to make dc(1) exit with the \f[B]Q\f[R] command, so the sequence
923 \f[B],Q\f[R] will make dc(1) exit.
981 \f[B]0\f[R] in the top item) when dc(1) starts, dc(1) requires that each
982 register\[cq]s stack must always have at least one item; dc(1) will give
1045 Unlike most other dc(1) implentations, this dc(1) provides nearly
1059 When dc(1) encounters an error or a signal that it has a non\-default
1072 Thus, when dc(1) resets, it skips any remaining code waiting to be
1078 Most dc(1) implementations use \f[B]char\f[R] types to calculate the
1080 This dc(1) does something different.
1092 In addition, this dc(1) uses an even larger integer for overflow
1097 The following are the limits on dc(1):
1158 As \f[B]non\-portable extensions\f[R], dc(1) recognizes the following
1162 This is another way to give command\-line arguments to dc(1).
1170 functions that the user might want every time dc(1) runs.
1177 For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
1179 \[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
1185 `dc' file.dc\[rq]\f[R], and vice versa if you have a file with double
1196 (\f[B]2\[ha]16\-1\f[R]), dc(1) will output lines to that length,
1207 If dc(1) is not in interactive mode (see the \f[B]INTERACTIVE MODE\f[R]
1208 section), then this environment variable has no effect because dc(1)
1212 However, when dc(1) is in interactive mode, then if this environment
1213 variable exists and contains an integer, a non\-zero value makes dc(1)
1214 reset on \f[B]SIGINT\f[R], rather than exit, and zero makes dc(1) exit.
1216 then dc(1) will exit on \f[B]SIGINT\f[R].
1228 exists and contains an integer, then a non\-zero value makes dc(1) use
1229 TTY mode, and zero makes dc(1) not use TTY mode.
1241 exists and contains an integer, a non\-zero value makes dc(1) use a
1242 prompt, and zero or a non\-integer makes dc(1) not use a prompt.
1256 contains an integer, a non\-zero value makes dc(1) exit after executing
1257 the expressions and expression files, and a zero value makes dc(1) not
1267 contains an integer, a non\-zero value makes dc(1) clamp digits that are
1329 characters (dc(1) only accepts ASCII characters), attempting to open a
1333 The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
1334 always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
1336 The other statuses will only be returned when dc(1) is not in
1343 These exit statuses allow dc(1) to be used in shell scripting with error
1347 Like bc(1), dc(1) has an interactive mode and a non\-interactive mode.
1353 In interactive mode, dc(1) attempts to recover from errors (see the
1362 available, and thus, dc(1) can turn on TTY mode, subject to some
1367 that environment variable contains a non\-zero integer, dc(1) will turn
1371 \f[I]not\f[R] a non\-zero integer, then dc(1) will not turn TTY mode on.
1403 Sending a \f[B]SIGINT\f[R] will cause dc(1) to do one of two things.
1405 If dc(1) is not in interactive mode (see the \f[B]INTERACTIVE MODE\f[R]
1408 an integer or it is zero, dc(1) will exit.
1410 However, if dc(1) is in interactive mode, and the
1412 then dc(1) will stop executing the current input and reset (see the
1416 If dc(1) is processing input from \f[B]stdin\f[R] in interactive mode,
1418 If dc(1) is processing input from a file in interactive mode, it will
1422 This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
1423 executing a file, it can seem as though dc(1) did not respond to the
1431 \f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
1436 The dc(1) utility operators and some behavior are compliant with the