What does 010001100101010101001110 actually say?

[yathis]

Its in the title of the thread subject but I wonder what it actually says.

[Hazy125]

fun

[yathis]

Do you break it down into 4 bits or numbers or what?

Is it a bit or a byte.

[PeachyUwUSenpai]

FUN and yes its a byte

[yathis]

0100 0110 = F

0101 0101 = U

0100 1110 = N

[SCHISCHKA]

Na google translate is saying oh one oh oh oh oh one one oh

[sgzUk74r3T3BCGmRJ]

?

[Dat Guy]

3 hours ago, yathis said:

Its in the title of the thread subject but I wonder what it actually says.

That depends on your platform's endianness. Everyone who said it says "FUN" has assumed a certain platform without knowing yours. We need more information to answer your question reliably.

[straight_stewie]

2 hours ago, Dat Guy said:

That depends on your platform's endianness. Everyone who said it says "FUN" has assumed a certain platform without knowing yours. We need more information to answer your question reliably.

There is only one true endianness.

[Dat Guy]

True, but "010001100101010101001110" is not "FUN" on middle-endian systems.

[2FA]

It says "5ZWO".

[yathis]

Which code are you using?

[beanhubbleday]

01100111 01100101 01110100 00100000 01110010 01100101 01101011 01110100 00100000 01101011
01101001 01100100 01111010

Edited March 8, 2017 by JackHubbleday
Added spaces, because I'm nice :)

[Unimportant]

It can also mean:

 

01000110 = 0x46 =                    inc    esi
01010101 = 0x55 =                    push   ebp
01001110 = 0x4e =                    dec    esi

 

in x86 assembler.

Binary can mean anything depending on context.

[Claryn]

On 6.3.2017 at 0:22 PM, sgzUk74r3T3BCGmRJ said:

snip

Kinda hope you had this stored somewhere! Anyways, credz for a good explanation of the "algorithm" for translating binary-ASCII as a mortal.

[Yamoto42]

On 3/6/2017 at 8:06 AM, Dat Guy said:

That depends on your platform's endianness. Everyone who said it says "FUN" has assumed a certain platform without knowing yours. We need more information to answer your question reliably.

Imma have to disagree on that one...

A byte string has no endianness.  When printed as the value pointed to by a char* it will produce the same output regardless of big or little endian systems...apart from the lack of null termination...so who knows what it will actually print on any system after the first three symbols...and even that much is assuming it even hits a null byte before an unallocated page boundary...or at least fills the stdout buffer forcing a flush first...  Multi-byte data types will vary, yes...but not char.