Description of problem:
bc doesn't know about 0x prefix for hex numbers, yet every other program on the
planet seems to
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(standard_in) 1: syntax error
Please see attached very simple patch which allows for hex literals.
The change would not create any problem with existing usage of bc.
Created attachment 131912 [details]
Patch to facilitate hexadecimal literals
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
bc maintainer is very stubborn and refuses to budge on this one
Fedora Core 4 is now completely unmaintained. These bugs can't be fixed in that
version. If the issue still persists in current Fedora Core, please reopen.
Thank you, and sorry about this.
Applicable to Fedora Core 6. Sorry about this.
Package Change Request
Package Name: bc
Updated Fedora Owners: email@example.com
bc uses [i,o]base variable for setting a [input,output] radix. dc controls
radixes by "[i,o]" as operations on a stack. So i do not think this is useful.
I think it is useful for users of bc. The obase/ibase is cumbersome. And it
makes it impossible to mix numbers with different base in same expression.
Like: "echo 0x1234+43 | bc"
How can you do this simply without my simple patch? More to the point - what
harm would it do?
BTW it has nothing to do with dc, Zdenek, because if you bothered to look at bc
code you would see that it doesn't use dc any more! Just RTFM!!!!
I know than it has nothing to do with dc. I just put it in comment how dc
controls radixes, nothing more.
Without your patch there is no simply way how to mix numbers with different base
in same expression.
I'll take a look.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
The patch was sent to the upstream.