Edit - Stack Overflow

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

I would slightly change case (C), or add a case (D), delivering final results to an end user. The output should be limited to digits that are expected to be correct and useful in the context of the application. Obviously, this cannot be done as a default, because it depends on the precision of the inputs and the numerical properties of the calculations, as well as the intended use of the data.

Patricia Shanahan
– Patricia Shanahan

2012-12-30 18:27:33 +00:00
Commented Dec 30, 2012 at 18:27
@PatriciaShanahan: I am receptive to changing or bifurcating case (C), but I am unclear on the distinction you want to make. The initial list describes the cases, with (C) being producing only some of the digits. I think you may be addressing the second list, which discusses further properties or purposes of the cases, and perhaps making a distinction between a language guessing at a good number of digits to use and a specific application developer planning a good number of digits to use. Could you clarify?

Eric Postpischil
– Eric Postpischil

2012-12-31 14:00:19 +00:00
Commented Dec 31, 2012 at 14:00
I was thinking mainly about the purpose of limiting the printed digits. Selecting the number of digits for delivering results to the end user is not just a matter of giving the reader a sense of the number. It is picking the digits that will actually be used, the digits that are the ultimate purpose of the whole computation. I felt that the description of C seemed far too casual for something of that extreme importance.

Patricia Shanahan
– Patricia Shanahan

2012-12-31 15:01:58 +00:00
Commented Dec 31, 2012 at 15:01

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »

Collectives™ on Stack Overflow