Lines Matching +full:disable +full:- +full:dc
21 The first bug is that `bc`/`dc` will exit on macOS when the terminal is resized.
26 The third bug is that value stack for `dc` was cleared on any error. However,
27 this is not how other `dc` behave. To bring `dc` more in line with other
126 feature for `dc`: there is now a command to query whether extended registers are
180 * A crash when `bc` and `dc` are built using editline, but history is not
184 * A failure to clear the tail call list in `dc` on error.
185 * A crash when attempting to swap characters in command-line history when no
211 The first memory bug could be reproduced by assigning a string to a non-local
213 non-local variable, which would still refer to a string in the previous version
217 built-in function. In certain cases, that was wrongly allowed, and the
221 The first feature was the addition of the `is_number()` built-in function (`u`
222 in `dc`) that returns 1 if the runtime argument is a number and 0 otherwise.
224 The second feature was the addition of the `is_string()` built-in function (`t`
225 in `dc`) that returns 1 if the runtime argument is a string and 0 otherwise.
227 These features were added because I realized that type-checking is necessary now
229 been assignable to variables in `dc`.
231 The last added feature is the ability of the `asciify()` built-in function in
233 character-by-character printing will not be necessary, and more strings than
234 just single-character ones will be able to be created.
245 This is a production release that fixes a build bug for cross-compilation.
247 Users that do not need cross-compilation do ***NOT*** need to upgrade.
253 * The `-l` option overrode the `-S` option.
254 * A double-free and crash when sending a `SIGINT` while executing expressions
255 given on the command-line.
261 Users that do not use `bcl` (use only `bc` and/or `dc`) do ***NOT*** need to
279 with the BSD `bc` and `dc`: turning off digit clamping when parsing numbers.
283 environment variables, and it can be set with the `-c` and `-C` command-line
289 the capability for multi-threading. This required a major version bump. I
293 To help with building, a convenience option (`-p`) to `configure.sh` was added
294 to build a `bc` and `dc` that is by default compatible with either the BSD `bc`
295 and `dc` or the GNU `bc` and `dc`.
322 editline, pass `-e` to `configure.sh`, and to use readline, pass `-r`.
324 Second, history support for Windows has been fixed and re-enabled.
326 Third, command-line options to set `scale`, `ibase`, `obase`, and `seed` were
352 file to `bc` using `-f` if that file had a multiline comment or string in it.
371 out-of-source builds and a `pkg-config` file for `bcl`.
396 * Fixed a bug with the `bc` banner and `-q`.
398 * Added a command-line flag (`-z`) to make `bc` and `dc` print leading zeroes on
399 numbers `-1 < x < 1`.
402 the use of `-z` or not.
405 * Added a command-line flag (`-L`) to disable wrapping when printing numbers.
448 allocation is retried. This is to make `bc` and `dc` more resilient to running
452 * Allowed integers with non-zero `scale` to be used with power, places, and
456 * Added a command to `dc` (`y`) to get the length of register stacks.
457 * Fixed multi-digit bugs in `lib2.bc`.
463 * Fixed bugs with the handling of register names in `dc`.
464 * Fixed bugs with multi-line comments and strings in both calculators.
465 * Added a new error type and message for `dc` when register stacks don't have
468 * Made `bc` and `dc` UTF-8 capable.
473 * Added the ability for users to have `bc` and `dc` quit on `SIGINT`.
474 * Added the ability for users to disable prompt and TTY mode by environment
478 * Added `dc`'s modular exponentiation and divmod to `bc`.
481 * Added `dc`'s asciify command and stream printing to `bc`.
482 * Added a command to `dc` (`Y`) to get the length of an array.
483 * Added a command to `dc` (`,`) to get the depth of the execution stack.
493 would not be set to `20` even if `-l` was used.
504 This is a production release with many fixes, a new command-line option, and a
507 * A bug was fixed in `dc`'s `P` command where the item on the stack was *not*
512 * A new command-line option, `-R` and `--no-read-prompt` was added to disable
513 just the prompt when using `read()` (`bc`) or `?` (`dc`).
549 The fixes for manuals fixed a bug where `--` was rendered as `-`.
553 This is a production release that fixes a divide-by-zero bug in `root()` in the
567 The changed behavior is the treatment of `-e` and `-f` when given through
568 `BC_ENV_ARGS` or `DC_ENV_ARGS`. Now `bc` and `dc` do not exit when those options
570 `bc` and `dc` still exit when they or their equivalents are given on the
571 command-line.
575 This is a production release that removes a small non-portable shell operation
579 Non-OpenBSD users do ***NOT*** need to upgrade, although NetBSD users may also
598 The two most important bugs were bugs that causes `dc` to access memory
599 out-of-bounds (crash in debug builds). This was found by upgrading to `afl++`
605 Third, some warnings by `scan-build` were found and eliminated. This needed one
606 big change: `bc` and `dc` now bail out as fast as possible on fatal errors
609 Fourth, the pseudo-random number now attempts to seed itself with `/dev/random`
612 Finally, this release has a few quality-of-life changes to the build system. The
634 bug was using the GNU `find` extension `-wholename`.
651 This is done with the `-a` option to `configure.sh`. The API for the library can
685 The behavior that was changed is that `bc` now exits when given `-e`, `-f`,
686 `--expression` or `--file`. However, if the last one of those is `-f-` (using
687 `stdin` as the file), `bc` does not exit. If `-f-` exists and is not the last of
688 the `-e` and `-f` options (and equivalents), `bc` gives a fatal error and exits.
693 Finally, I made it so `bc` does not print the header, though the `-q` and
694 `--quiet` options were kept for compatibility with GNU `bc`.
713 For package maintainers wishing to make use of the change, just pass `-l` to
727 The behavior that was adjusted was how code from the `-e` and `-f` arguments
729 in this release, they are now executed line-by-line.
733 clean-up function was not getting called. This release fixes that bug.
735 The second bug is in how `dc` handled input from `stdin`. This affected `bc` as
738 The third fixed bug was that `bc` and `dc` could `abort()` (in debug mode) when
749 The last two bugs were crashes in `dc` that resulted from mishandling of
760 Before this release, `bc` and `dc` only used one manpage each that referred to
818 output the wrong numbers if there was any non-zero digit after.
842 Fifth, the interpreter received a speedup to make performance on non-math-heavy
860 arbitary-precision numbers). If a `BcNum` has the default capacity of
861 `BC_NUM_DEF_SIZE` (32 on 64-bit and 16 on 32-bit) when it is freed, it is added
868 minimum allocation size on Linux, which is either 32 bytes (64-bit musl), 24
869 bytes (64-bit glibc), 16 bytes (32-bit musl), or 12 bytes (32-bit glibc). Since
872 of `BC_NUM_DEF_SIZE` on 64-bit systems was changed to 32 bytes.
874 On top of that, at least on 64-bit, `BC_NUM_DEF_SIZE` supports numbers with
882 (For 32-bit, these numbers are either 32 integer digits or 12 integer digits and
884 32-bit system seems a little pointless since 12 digits is just under a trillion
885 and 20 fractional digits is still enough for about any use since `10^-20` light
903 `BC_NUM_DEF_SIZE` bigger on 64-bit systems, since the vast majority of numbers
908 from a polling approach to signal handling to an interrupt-based approach.
930 builds will be smaller, but non-static builds will be bigger, though they will
946 unwinding is well-tested. (Errors are tested heavily in the test suite.)
958 The `length()` built-in function can take either a number or an array. If it
995 There is only one new feature: **`bc` now has a built-in pseudo-random number
1003 It also outputs 32 bits on 32-bit platforms and 64 bits on 64-bit platforms, far
1008 size. (As of the time of release, the largest pseudo-random number generated by
1011 ***IMPORTANT: read the [`bc` manual][9] and the [`dc` manual][10] to find out
1063 CC="gcc -O3 -march=native" ./configure.sh
1068 and `CFLAGS` will be "-O3 -march=native".
1079 * An option for `configure.sh` was added to disable long options if
1091 This is a production release primarily aimed at improving `dc`.
1093 * A couple of copy and paste errors in the [`dc` manual][10] were fixed.
1094 * `dc` startup was optimized by making sure it didn't have to set up `bc`-only
1096 * The `bc` `&&` and `||` operators were made available to `dc` through the `M`
1098 * `dc` macros were changed to be tail call-optimized.
1102 new macro. This change was made to stop `dc` from consuming more and more memory
1111 making it possible to disable binary stripping. Other users do *not* need to
1116 This is a production release. It fixes a bug that caused `-1000000000 < -1` to
1140 This is a non-critical release; it just changes the build system, and in
1141 non-breaking ways:
1170 1. A `dc` bug that caused stack mishandling was fixed.
1176 7. A `dc` bug where strings, in a rare case, were mishandled in parsing was
1182 2. An option was added to the build to disable printing of prompts.
1208 This is a production, bug-fix release.
1239 billion (`2^31-1`) `SIGINT`'s, but I saw it and had to fix it.
1245 1. A slight bug in `dc`'s interactive mode was fixed.
1247 3. **The `-P`/`--no-prompt` option** was added for users that do not want a
1250 5. `dc` got its own read prompt: `?> `.
1266 3. A **POSIX shell-compatible script was added as an alternative to compiling
1268 between the two can be found by running `./configure.sh --help` or reading
1273 6. `dc` was given the ability to **use the environment variable
1275 7. `dc` was also given the ability to **use the `-i` or `--interactive`**
1280 11. The **built-in functions `maxibase()`, `maxobase()`, and `maxscale()`** (the
1281 commands `T`, `U`, `V` in `dc`, respectively) were added to allow scripts to
1305 shell-compatible, and also updates a man page that should have been updated a
1339 with the `-g` command-line option. (See the [`bc` manual][9] for more
1347 [`bc` manual][9] and the [`dc` manual][10] for details.
1349 notation**. See the [`bc` manual][9] and the [`dc` manual][10] for details.
1363 `dc` tests could not be run in parallel.
1381 shell-compatible configure script ([`configure.sh`][6]) to generate a POSIX
1382 make-compatible `Makefile`, which means that `bc` and `dc` now build out of
1383 the box on any POSIX-compatible system.
1384 2. Out-of-memory and output errors now cause the `bc` to report the error,
1393 8. A bug was removed where `dc` could have been selected, but the internal
1394 `#define` that returned `true` for a query about `dc` would not have
1398 [UTF-8 aware fork][7] of [`linenoise`][8], which has been customized with
1406 15. **`abs()` (`b` command for `dc`) was added as a builtin.**
1413 20. **GNU-style array references were added as a supported feature.**
1415 22. **New operators were added**: `$` (`$` for `dc`), `@` (`@` for `dc`), `@=`,
1416 `<<` (`H` for `dc`), `<<=`, `>>` (`h` for `dc`), and `>>=`. See the
1417 [`bc` manual][9] and the [`dc` manual][10] for more details.
1422 25. **Support for GNU-style void functions was added.**
1425 28. `dc` was given an explicit negation command.
1426 29. `dc` was changed to be able to handle strings in arrays.
1477 This is the first non-beta release. `bc` is ready for production use.
1481 1. `dc` has been added. It has been tested even more thoroughly than `bc` was
1504 `bc` and `dc` have together been run through 30+ million random tests.
1515 18. `bc` was made fully compliant with POSIX when the `-s` flag is used or
1552 This is the first Release Candidate for 1.0. `bc` is complete, with `dc`, but it
1569 [1]: https://docs.microsoft.com/en-us/windows/wsl/install-win10
1575 [7]: https://github.com/rain-1/linenoise-mob
1578 [10]: ./manuals/dc/A.1.md
1579 [11]: https://scan.coverity.com/projects/gavinhoward-bc
1584 [16]: ./manuals/bc/A.1.md#extended-library
1588 [20]: https://github.com/apjanke/ronn-ng