如何指定 setprecision 舍入

How to specify setprecision rounding(如何指定 setprecision 舍入)
本文介绍了如何指定 setprecision 舍入的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当流到标准输出时,我可以指定 setprecision 来舍入双精度值吗?

Can I specify setprecision to round double values when stream to std output?

ofile << std::setprecision(12) << total_run_time/TIME << "
";

输出:0.756247615801

Output: 0.756247615801

ofile << std::setprecision(6)<< total_run_time/TIME << "
";

输出:0.756248

但我需要输出为 0.756247

谢谢

推荐答案

还有中的std::fesetround,设置舍入方向:

There is also std::fesetround from <cfenv>, which sets the rounding direction:

#include <iostream>
#include <iomanip>
#include <cmath>
#include <cfenv>

int main () {
    double runtime = 0.756247615801;

    // Set rounding direction and output with some precision:
    const auto prev_round = std::fegetround();
    std::fesetround(FE_DOWNWARD);    
    std::cout << "desired: " << std::setprecision(6) << runtime << "
";

    // Restore previous rounding direction and output for testing:
    std::fesetround(prev_round);
    std::cout << "default: " << std::setprecision(6) << runtime << "
";
}

(请注意,这些不是我推荐的评论,它们只是用于辅导目的)

输出:

desired: 0.756247
default: 0.756248

重要提示:我没有在标准中发现任何关于浮动类型的 operator<< 重载遵守舍入方向.

Important note, though: I did not find any mention in the standard, that the operator<< overloads for floating types have to honour the rounding direction.

这篇关于如何指定 setprecision 舍入的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Rising edge interrupt triggering multiple times on STM32 Nucleo(在STM32 Nucleo上多次触发上升沿中断)
How to use va_list correctly in a sequence of wrapper functions calls?(如何在一系列包装函数调用中正确使用 va_list?)
OpenGL Perspective Projection Clipping Polygon with Vertex Outside Frustum = Wrong texture mapping?(OpenGL透视投影裁剪多边形,顶点在视锥外=错误的纹理映射?)
How does one properly deserialize a byte array back into an object in C++?(如何正确地将字节数组反序列化回 C++ 中的对象?)
What free tiniest flash file system could you advice for embedded system?(您可以为嵌入式系统推荐什么免费的最小闪存文件系统?)
Volatile member variables vs. volatile object?(易失性成员变量与易失性对象?)