Does bc support hex calculations?
I'm trying to do a hex calculation directly with bc, I already specified the scale.
echo 'scale=16;c06b1000-c06a5e78' | bc
But I still get a zero. What could be wrong?
bc calculator
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
add a comment |
I'm trying to do a hex calculation directly with bc, I already specified the scale.
echo 'scale=16;c06b1000-c06a5e78' | bc
But I still get a zero. What could be wrong?
bc calculator
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09
add a comment |
I'm trying to do a hex calculation directly with bc, I already specified the scale.
echo 'scale=16;c06b1000-c06a5e78' | bc
But I still get a zero. What could be wrong?
bc calculator
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
I'm trying to do a hex calculation directly with bc, I already specified the scale.
echo 'scale=16;c06b1000-c06a5e78' | bc
But I still get a zero. What could be wrong?
bc calculator
bc calculator
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
edited Sep 5 '14 at 13:13
terdon♦
129k32253428
129k32253428
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
asked Oct 4 '12 at 6:55
daisydaisy
28.5k49169302
28.5k49169302
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09
add a comment |
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09
add a comment |
1 Answer
1
active
oldest
votes
echo 'ibase=16;C06D1000-C06A5E78' | bc
176520
Note that only UPPER CASE hex digits are supported as lower case ones would conflict with function and variable names, which is why you got 0 in your example (var1 - var2)
If you need the answer in hex too, just set the obase variable:
echo 'obase=16;ibase=16;C06D1000-C06A5E78' | bc
2B188
PS: FYI scale isn't designed for conversion base. From man bc:
scale defines how some operations use digits after the decimal point.
The default value of scale is 0.
edited Jan 10 at 14:45
Roland
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f49850%2fdoes-bc-support-hex-calculations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
echo 'ibase=16;C06D1000-C06A5E78' | bc
176520
Note that only UPPER CASE hex digits are supported as lower case ones would conflict with function and variable names, which is why you got 0 in your example (var1 - var2)
If you need the answer in hex too, just set the obase variable:
echo 'obase=16;ibase=16;C06D1000-C06A5E78' | bc
2B188
PS: FYI scale isn't designed for conversion base. From man bc:
scale defines how some operations use digits after the decimal point.
The default value of scale is 0.
edited Jan 10 at 14:45
Roland
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
add a comment |
echo 'ibase=16;C06D1000-C06A5E78' | bc
176520
Note that only UPPER CASE hex digits are supported as lower case ones would conflict with function and variable names, which is why you got 0 in your example (var1 - var2)
If you need the answer in hex too, just set the obase variable:
echo 'obase=16;ibase=16;C06D1000-C06A5E78' | bc
2B188
PS: FYI scale isn't designed for conversion base. From man bc:
scale defines how some operations use digits after the decimal point.
The default value of scale is 0.
edited Jan 10 at 14:45
Roland
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
add a comment |
echo 'ibase=16;C06D1000-C06A5E78' | bc
176520
Note that only UPPER CASE hex digits are supported as lower case ones would conflict with function and variable names, which is why you got 0 in your example (var1 - var2)
If you need the answer in hex too, just set the obase variable:
echo 'obase=16;ibase=16;C06D1000-C06A5E78' | bc
2B188
PS: FYI scale isn't designed for conversion base. From man bc:
scale defines how some operations use digits after the decimal point.
The default value of scale is 0.
edited Jan 10 at 14:45
Roland
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
echo 'ibase=16;C06D1000-C06A5E78' | bc
176520
Note that only UPPER CASE hex digits are supported as lower case ones would conflict with function and variable names, which is why you got 0 in your example (var1 - var2)
If you need the answer in hex too, just set the obase variable:
echo 'obase=16;ibase=16;C06D1000-C06A5E78' | bc
2B188
PS: FYI scale isn't designed for conversion base. From man bc:
scale defines how some operations use digits after the decimal point.
The default value of scale is 0.
edited Jan 10 at 14:45
Roland
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
edited Jan 10 at 14:45
Roland
1105
edited Jan 10 at 14:45
Roland
1105
edited Jan 10 at 14:45
Roland
1105
1105
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
answered Oct 4 '12 at 7:07
rushrush
19.1k46395
19.1k46395
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
add a comment |
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
So the real answer on 'what could be wrong' is that bc only supports UPPER CASE for the hex digits, with credits to editor Stephane.
– Roland
Jan 10 at 10:23
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f49850%2fdoes-bc-support-hex-calculations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
While not technically an answer to your question, you might want to consider moo(1) instead of bc(1).
– user24323
Oct 6 '12 at 2:09