`Lol I told you IDK

Typically i just give a lower bound

And you know what? Python allows you comparing them with ==

not sure how python stores their values tbh but there is probably some limit when it goes yeah it’s probably equal

@linuxer4fun Btw, I may have been saying it in a stupid way, but I meant this https://en.wikibooks.org/wiki/X86_Assembly/Intrinsic_Data_Types "Originally, floating point was not part of the main processor, requiring the use of emulating software. However, there were floating point coprocessors that allowed operations on this data-type, and starting with the 486DX, were integrated directly with the CPU. " Therefore, CPU supports floats on a hadware level And I also included flags cuz it's... you get it

Strictly speaking, assembly has no predefined data types like higher-level programming languages.

Strictly speaking, assembly has no predefined data types like higher-level programming languages.

Strictly speaking, assembly has no predefined data types like higher-level programming languages.

word dword qword

"That said, one can group data in assembly into two categories: integer and floating point." I am the one

they arent rlly data types but are the most similar

double and quadruple

That said, one can group data in assembly into two categories: integer and floating point. While you could load a floating point value into a register and treat it like an integer, the results would be unexpected, so it is best to keep them separate. please don't quote ouf ot context

The result can be unexpected. This is what I told you. In my world "you can't do it" equals "the result would be unexpected "

this is why you suck

floats are stored by ieee754 in memory

floats are stored by ieee754 in memory

ieee754 standard*

they are stored as binary

So, you would agree it's another data type if it was stored... not in binary? :D

they are stored as binary

You said they are stored in binary... does that define a data type?

floats are like just fancy scientific notation

a datatype is a pattern by which the compiler knows how to associate a memory map to "something"

Okay, then we can't argue about types if there are no compilers

which is my point from the fucking beginning

My point was that... we see word of bits It can be an integer(signed and unsigned), a float, or a bunch of flags And that's pretty it

*a byte

*a byte

First bit - sign Next 4 bits - coefficient Last 3 bits - exponent typically floats and ints uses 4 bytes(or ieee754 double precision that is 8 bytes)

First bit - sign Next 4 bits - coefficient Last 3 bits - exponent typically floats and ints uses 4 bytes(or ieee754 double precision that is 8 bytes)

coefficient and exponent both are a bit bigger 😉

Nice idea for a library, but makes no sense

If we need to somehow stuff a float in 1 byte

ITS LITTERRALLY WHAT A FLOAT IS YOU DUMBFUCK

for astronomers: First bit - sign Last 7 bits - exponent as a questiobable signed integer xd

ITS LITTERRALLY WHAT A FLOAT IS YOU DUMBFUCK

Angry maxi is angry

let's make 9 bit floats

implied by the name

lets make characters 7 bits

Wdym?

angry maxi can only be angry

But is maxi always angry?