View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0031862 | Community | OCCT:Coding | public | 2020-10-19 11:55 | 2021-09-05 23:28 |
Reporter | BenjaminBihler | Assigned To | bugmaster | ||
Priority | normal | Severity | minor | ||
Status | closed | Resolution | unable to reproduce | ||
Platform | MinGW-w64 | OS | Windows | ||
Product Version | 7.5.0 | ||||
Target Version | 7.5.0 | ||||
Summary | 0031862: [REGRESSION] Coding - Flags of output stream are modified | ||||
Description | Since the revision V7_5_0_beta the output of my program has changed. When printing floats to std::cout, more digits than before are displayed. After digging into the OCCT code, I found out that the flag modifications happen in AppDef_Variational::Dump. This can be prevented by storing the stream flags and restoring them later. | ||||
Tags | No tags attached. | ||||
Test case number | |||||
|
Branch CR31862 has been created by BenjaminBihler. SHA-1: be5b376612b439ad7b337b033270febae772005b Detailed log of new commits: Author: Benjamin Bihler Date: Mon Oct 19 11:09:13 2020 +0200 0031862: [REGRESSION] Coding - Flags of output stream are modified Added RAII class to restore stream flags after dump. |
|
Here https://stackoverflow.com/questions/2273330/restore-the-state-of-stdcout-after-manipulating-it are several alternative proposals how to solve that issue, if you are not content with my solution. |
|
> I found out that the flag modifications happen in AppDef_Variational::Dump. I don't think that AppDef_Variational::Dump() could be the cause - no changes to the logic itself have been done recently there (0030895 targeting OCCT 7.4.0 doesn't seem should change behavior), and I don't think the method is called at all in your context (could you check this with a breakpoint?). |
|
You are probably right. Right now I even cannot reproduce the problem! :-((( Sorry for a false issue report. I guess you can close the issue! (If I find the error again and I am sure where it comes from, I can reopen the issue.) |
|
Okay, I have found my error. It was definitely a misinterpretation. Please close the issue. |
|
Branch CR31862 has been deleted by kgv. SHA-1: be5b376612b439ad7b337b033270febae772005b |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-10-19 11:55 | BenjaminBihler | New Issue | |
2020-10-19 11:55 | BenjaminBihler | Assigned To | => BenjaminBihler |
2020-10-19 12:18 | git | Note Added: 0096052 | |
2020-10-19 12:19 | BenjaminBihler | Note Added: 0096053 | |
2020-10-19 12:19 | BenjaminBihler | Note Edited: 0096053 | |
2020-10-19 12:20 | BenjaminBihler | Note Edited: 0096053 | |
2020-10-19 12:20 | BenjaminBihler | Note Edited: 0096053 | |
2020-10-19 12:22 | kgv | Note Added: 0096054 | |
2020-10-19 12:22 | kgv | Relationship added | related to 0030895 |
2020-10-19 12:36 | kgv | Note Edited: 0096054 | |
2020-10-19 12:38 | BenjaminBihler | Note Added: 0096055 | |
2020-10-19 12:38 | BenjaminBihler | Assigned To | BenjaminBihler => |
2020-10-19 12:38 | BenjaminBihler | Assigned To | => kgv |
2020-10-19 15:08 | BenjaminBihler | Note Added: 0096058 | |
2020-10-19 15:40 | kgv | Assigned To | kgv => bugmaster |
2020-10-19 15:40 | kgv | Status | new => feedback |
2020-10-19 15:40 | kgv | Resolution | open => unable to reproduce |
2020-10-20 10:04 | bugmaster | Status | feedback => closed |
2021-09-05 23:28 | git | Note Added: 0103840 |