Talk:Approximate equality: Difference between revisions

From Rosetta Code
Content added Content deleted
 
Line 1: Line 1:


==Can of worms==
==Can of worms==
uh-oh, you've opened a can of words here. I can remember in the far distant path, being lectured to about floating point/equality/closeness and I resolved to run and hide if I could in the future :-)<br>
uh-oh, you've opened a can of words here. I can remember in the far distant past, being lectured to about floating point/equality/closeness and I resolved to run and hide if I could in the future :-)<br>
Firstly, you can't leave people to find out how Python does it, if you want them to use a specific method then you need to add the description to the task.<br>
Firstly, you can't leave people to find out how Python does it, if you want them to use a specific method then you need to add the description to the task.<br>
Second. Approximation depends on circumstances. If the compared vary exponentially ar non-linearly, or ... then one may end up with different, but more usable definitions of approximately equal.<br>
Second. Approximation depends on circumstances. If the compared vary exponentially ar non-linearly, or ... then one may end up with different, but more usable definitions of approximately equal.<br>

Revision as of 15:18, 2 September 2019

Can of worms

uh-oh, you've opened a can of words here. I can remember in the far distant past, being lectured to about floating point/equality/closeness and I resolved to run and hide if I could in the future :-)
Firstly, you can't leave people to find out how Python does it, if you want them to use a specific method then you need to add the description to the task.
Second. Approximation depends on circumstances. If the compared vary exponentially ar non-linearly, or ... then one may end up with different, but more usable definitions of approximately equal.
--Paddy3118 (talk) 12:08, 2 September 2019 (UTC)