>wincucks will defend this
>"b-b-b-but muhhh IEEE!"
kek
Wincucks will defend this
>implying winniggers understand that image
99% of Micropenis Shitdows users are non-programmers. They're stupid /v/tard normies who couldn't write a hello world program in C and only care about muh gayemz.
>duhhh floating point numbers are imprecise, this is all micro$ofts fault
okay, this is epic
Writeline parameters convert that shit to integer to string
Just use a CAS if you don't want this to happen, it also has nothing to do with Windows.
Obviously not all real numbers can be expressed in 64 bits, why are you surprised?
Why?
>I don't understand floating point numbers
the post
>99% of Micropenis Shitdows users are non-programmers.
99% of the world are non-programmers.
Yeah no shit, same thing in Python
It is independent of the language used, this is about representing numbers in hardware.
You can avoid this in any language you want, you just need to use infinite precision types.
I know, it has to do with floating points and how much you alocate to store them. Just showing blatan OP bait that it's not related to Windows
floating point numbers are the big gay
1.every language will give you the same result
2.why the fuck are you using doubles for this precision?why dont use use decimals?or are you simply this retarded?
3.if you would actually know how floating point numbers are represented in memory then you wouldnt have to embarass yourself on a taiwanian gay-porn sharing forum
jesus fucking christ i wish we could just ban everyone on this board who doesnt work in IT.
>comparing floating-point numbers using binary equality operator
>on any fucking programming language
I detest calling myself as a programmer, when people like you are calling themselves as one. Ever heard of epsilon-closeness?
>Is 1 a 1?
>Yep
what is the problem here?
Feature, not bug
Decimal types are available if you expect different behavior
What does this have to do with IEEE
IEEE-754 is standard regarding floating points
...no