Handle mpc80 generation where zero padding of 9.999 was writing 010.00 - #19
Open
petervanwylen wants to merge 1 commit into
Open
petervanwylen wants to merge 1 commit into
petervanwylen wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I found a unique situation where if day was 9.9999996 or higher, rasec was 9.9996 or higher or decsec was 9.996 or higher, the current would would write out something like 010.00 or 010.000 because the if statement was padding it and then the fixed setprecision was rounding up to 10. Using setfill and setw with setprecision fixes this problem. I hope this helps!