Converting Boost Multiprecision to a string with current locale settings












0















I'm working with the boost cpp_dec_float class, but can't get a string out of it with the correct regional settings (decimal symbol and grouping symbol).



Looking at the boost code, it looks like the internal str()-function always inserts a '.' character as decimal point. See format_float_string in number_base.



This is what I get with a regular double:



double d = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << d;
std::cout << ss.str() << std::endl;


outputs 1.494,330000



Trying the same with dec_float:



boost::multiprecision::cpp_dec_float_50 df = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << df;
std::cout << ss.str() << std::endl;


outputs 1494.330000



I'm looking for a solution that avoids converting the dec_float back to a double, as that would introduce some inaccuracy.










share|improve this question























  • I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

    – user14717
    Dec 5 '18 at 0:53
















0















I'm working with the boost cpp_dec_float class, but can't get a string out of it with the correct regional settings (decimal symbol and grouping symbol).



Looking at the boost code, it looks like the internal str()-function always inserts a '.' character as decimal point. See format_float_string in number_base.



This is what I get with a regular double:



double d = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << d;
std::cout << ss.str() << std::endl;


outputs 1.494,330000



Trying the same with dec_float:



boost::multiprecision::cpp_dec_float_50 df = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << df;
std::cout << ss.str() << std::endl;


outputs 1494.330000



I'm looking for a solution that avoids converting the dec_float back to a double, as that would introduce some inaccuracy.










share|improve this question























  • I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

    – user14717
    Dec 5 '18 at 0:53














0












0








0








I'm working with the boost cpp_dec_float class, but can't get a string out of it with the correct regional settings (decimal symbol and grouping symbol).



Looking at the boost code, it looks like the internal str()-function always inserts a '.' character as decimal point. See format_float_string in number_base.



This is what I get with a regular double:



double d = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << d;
std::cout << ss.str() << std::endl;


outputs 1.494,330000



Trying the same with dec_float:



boost::multiprecision::cpp_dec_float_50 df = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << df;
std::cout << ss.str() << std::endl;


outputs 1494.330000



I'm looking for a solution that avoids converting the dec_float back to a double, as that would introduce some inaccuracy.










share|improve this question














I'm working with the boost cpp_dec_float class, but can't get a string out of it with the correct regional settings (decimal symbol and grouping symbol).



Looking at the boost code, it looks like the internal str()-function always inserts a '.' character as decimal point. See format_float_string in number_base.



This is what I get with a regular double:



double d = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << d;
std::cout << ss.str() << std::endl;


outputs 1.494,330000



Trying the same with dec_float:



boost::multiprecision::cpp_dec_float_50 df = 1494.33;
std::stringstream ss;
ss.imbue(std::locale(""));
ss << std::fixed << std::setprecision(6) << df;
std::cout << ss.str() << std::endl;


outputs 1494.330000



I'm looking for a solution that avoids converting the dec_float back to a double, as that would introduce some inaccuracy.







c++ boost boost-multiprecision






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 27 '18 at 9:54









ShalieShalie

111




111













  • I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

    – user14717
    Dec 5 '18 at 0:53



















  • I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

    – user14717
    Dec 5 '18 at 0:53

















I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

– user14717
Dec 5 '18 at 0:53





I doubt it has been implemented. You could submit a github issue: github.com/boostorg/multiprecision

– user14717
Dec 5 '18 at 0:53












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496971%2fconverting-boost-multiprecision-to-a-string-with-current-locale-settings%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496971%2fconverting-boost-multiprecision-to-a-string-with-current-locale-settings%23new-answer', 'question_page');
}
);

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