Lines Matching refs:bc
21 The first bug is that `bc`/`dc` will exit on macOS when the terminal is resized.
35 The bug was that `bc` attempted to jump out when flushing `stdout` on exit, but
49 This is a production release to fix problems in the `bc` manual.
120 This is a production release that fixes a `bc` dependency loop for minimal
146 `tests/bc/scripts/timeconst.bc` doesn't exist. This should only affect
155 This is a production release that moves `bc` to <https://git.gavinhoward.com>.
166 parameter had the same name as the array whose element was used, `bc` would grab
180 * A crash when `bc` and `dc` are built using editline, but history is not
199 This is a production release that fixes a discrepancy from the `bc` standard,
202 The discrepancy from the `bc` standard was with regards to the behavior of the
203 `quit` command. This `bc` used to quit whenever it encountered `quit` during
204 parsing, even if it was parsing a full file. Now, `bc` only quits when
208 This behavior is slightly different from GNU `bc`, but users will only notice
228 that strings can be assigned to variables in `bc` and because they've always
232 `bc` to convert a full array of numbers into a string. This means that
261 Users that do not use `bcl` (use only `bc` and/or `dc`) do ***NOT*** need to
277 This is a production release that fixes an oversight in the `bc` parser (that
279 with the BSD `bc` and `dc`: turning off digit clamping when parsing numbers.
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`.
336 This is a production release that fixes this `bc`'s behavior on `^D` to match
337 GNU `bc`.
352 file to `bc` using `-f` if that file had a multiline comment or string in it.
366 was because `bc` was too strict.
385 exists in all versions of `bc`.
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
400 * Added four functions to `lib2.bc` (`plz()`, `plznl()`, `pnlz()`, and
413 The test was one that tested whether `bc` fails gracefully when it can't
420 However, this `bc` uses all of the memory it allocates (at least at page
444 digit was left, something I blindly copied from GNU `bc`, like a fool.
448 allocation is retried. This is to make `bc` and `dc` more resilient to running
454 * Added greatest common divisor and least common multiple to `lib2.bc`.
457 * Fixed multi-digit bugs in `lib2.bc`.
460 preferences for. This includes the `bc` banner, resetting on `SIGINT`, TTY
468 * Made `bc` and `dc` UTF-8 capable.
473 * Added the ability for users to have `bc` and `dc` quit on `SIGINT`.
478 * Added `dc`'s modular exponentiation and divmod to `bc`.
480 them to functions in `bc`.
481 * Added `dc`'s asciify command and stream printing to `bc`.
485 right rotate, and mod functions to `lib2.bc`.
486 * Added the functions `s2u(x)` and `s2un(x,n)`, to `lib2.bc`.
494 2. When using history, `bc` failed to respond properly to `SIGSTOP` and
513 just the prompt when using `read()` (`bc`) or `?` (`dc`).
546 compatibility with other `bc`'s, and the expectations of users, I decided to
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
606 big change: `bc` and `dc` now bail out as fast as possible on fatal errors
650 The major addition is a way to build a version of `bc`'s math code as a library.
658 If the library has API breaking changes, the major version of `bc` will be
671 This is a production release that fixes the Chinese locales (which caused `bc`
672 to crash) and a crash caused by `bc` executing code when it should not have been
685 The behavior that was changed is that `bc` now exits when given `-e`, `-f`,
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`.
698 This is a production release that fixes one minor bug: if `bc` was invoked like
702 echo "if (1 < 3) 1" | bc
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
742 The fourth bug fixed was that `bc` could leave extra items on the stack and
746 The next two bugs were bugs in `bc`'s parser that caused crashes when executing
760 Before this release, `bc` and `dc` only used one manpage each that referred to
782 The second change is to make the new implementation of `ceil()` in `lib2.bc`
792 on old locale files. Unfortunately, `bc` cannot use any locale files except the
794 running tests during install. **If `bc` segfaults while running arg tests when
799 this is done, `bc` should install without problems.*
805 three major bug fixes, and a complete redesign of `bc`'s error and signal
809 The first major bug fix was in how `bc` executed files. Previously, a whole file
812 before the definition referred to the previous function, this `bc` would replace
816 The second major bug fix was in `bc`'s `lib2.bc`. The `ceil()` function had a
824 Beyond that, this `bc` got several improvements that both sped it up, improved
827 First, the requirements for `bc` were pushed back to POSIX 2008. `bc` uses one
834 `bc` from allocating a large set of memory when `bc` starts.
843 scripts more competitive with GNU `bc`. While improvements did, in fact, get it
854 Second, since the current `bc` function is the one that stores constants and
859 Third, `bc` tries to reuse `BcNum`'s (the internal representation of
876 should be more than enough for most cases since `bc`'s default `scale` values
896 worse than `bc` did in `2.7.2`. Another was putting any `BcNum` on the reuse
906 Last of all, `bc`'s signal handling underwent a complete redesign. (This is the
915 `main()`, which just returns. If `bc` is currently executing code that cannot be
925 (There are only some 3 functions in `bc` that push and pop a `jmp_buf` twice.)
927 As a side effect of this change, I had to eliminate the use of `stdio.h` in `bc`
936 Another reason for this change is that my `bc` should *always* behave correctly
963 **ALL USERS SHOULD UPDATE `bc`**.
979 every platform, an adapted version of [`optparse`][17] was added. Now, `bc`
995 There is only one new feature: **`bc` now has a built-in pseudo-random number
1009 this `bc` was generated with a bound of `2^(2^20)`.)
1011 ***IMPORTANT: read the [`bc` manual][9] and the [`dc` manual][10] to find out
1016 On top of that, four functions were added to `bc`'s [extended math library][16]
1029 The bug was that when `bc` was built without long options, it would give a fatal
1037 No source code changed; the only thing that changed was `lib2.bc`.
1049 Portuguese locales. No `bc` code was changed.
1075 in the `bc` build system. No `bc` code was changed.
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`
1121 **ALL USERS SHOULD UPDATE `bc`**.
1174 5. A `bc` bug, mishandling of array arguments to functions, was fixed.
1186 (mostly) removed (see below), `bc` would leave extra values on its stack for
1189 even buggy behavior, but they would cause `bc` to take more memory than it
1194 1. The need for pop instructions in `bc` was removed.
1202 ***NOTE***: This is the last release with new features because this `bc` is now
1204 added to this `bc`.
1223 had noticed that GNU `bc` returned an error, correctly, but I thought it was
1224 wrong simply because that's not what my `bc` did. I saw it again later and had a
1225 double take. I checked for real, finally, and found out that my `bc` was wrong
1257 out, I do not plan on adding any more features to this `bc`; I believe that it
1291 This `bc` should now be the fastest `bc` available, but I may be wrong.
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.
1362 This release contains a fix for a bug in the test suite where `bc` tests and
1382 make-compatible `Makefile`, which means that `bc` and `dc` now build out of
1384 2. Out-of-memory and output errors now cause the `bc` to report the error,
1399 `bc`'s own data structures and signal handling.
1417 [`bc` manual][9] and the [`dc` manual][10] for more details.
1419 makes it so I can replace my desktop calculator with this `bc`. See the
1420 [`bc` manual][3] for more details.
1424 27. Precedence for the or (`||`) operator was changed to match GNU `bc`.
1443 release candidate meant specifically to test if `bc` works on FreeBSD. The new
1449 release candidate meant specifically to test if `bc` works on FreeBSD. The new
1455 release candidate meant specifically to test if `bc` works on FreeBSD. The new
1461 release candidate meant specifically to test if `bc` works on FreeBSD. The new
1467 specifically to test if `bc` works on FreeBSD. The new code has not been tested as
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
1484 2. `bc` has been more thoroughly tested. An entire section of the test suite
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
1518 20. `bc` now checks that files it is given are not directories.
1552 This is the first Release Candidate for 1.0. `bc` is complete, with `dc`, but it
1570 [2]: https://pkg.musl.cc/bc/
1577 [9]: ./manuals/bc/A.1.md
1579 [11]: https://scan.coverity.com/projects/gavinhoward-bc
1584 [16]: ./manuals/bc/A.1.md#extended-library