Dear 0x0000000:
Posted: Tue May 14, 2013 9:14 am
I am extremely curious to know what the fuck kind of architecture you're running where the width of a memory address is 28-bits.
Sincerely,
FalcoVorbis
Sincerely,
FalcoVorbis
Elysian Shadows
The Next Generation of 2D Roleplaying Games
http://forums.elysianshadows.com/
Dear 0x0000000:
Page 1 of 1
Re: Dear 0x0000000:
Posted: Tue May 14, 2013 1:41 pm
He is obviously using a notation where the number before the "x" is a bit and the ones after are 9-bit bytes.
Re: Dear 0x0000000:
Posted: Wed May 15, 2013 8:42 am
But that won't work either. A byte is represented as two characters: 0x00. One character is a nibble (4 bits).
Re: Dear 0x0000000:
Posted: Thu May 16, 2013 6:38 pm
lmfao
Re: Dear 0x0000000:
Posted: Sat May 18, 2013 10:48 am
[meta]Man, what a week. Finally found some time to write this...[/meta]
That is because his notation is not hexadecimal. Each digit is 9 bits, so the value goes from 0 to 511. The memory address 1364294724433924810 in binary would be 0001100000111100000110000001100000011000000110000001100002. If we choose UTF-9 as notation:
So, in 0x0000000's "1x63" notation, it would be represented as
That is because his notation is not hexadecimal. Each digit is 9 bits, so the value goes from 0 to 511. The memory address 1364294724433924810 in binary would be 0001100000111100000110000001100000011000000110000001100002. If we choose UTF-9 as notation:
Code: Select all
binary hex 1x63/utf-9
0 0x00 '0'
00110000 0x30 '0'
01111000 0x78 'x'
00110000 0x30 '0'
00110000 0x30 '0'
00110000 0x30 '0'
00110000 0x30 '0'
00110000 0x30 '0''0x0000000'I hope that clarifies.
Re: Dear 0x0000000:
Posted: Sun May 19, 2013 10:51 am
Aaaaaaah... Well fuck, that would work. 
Re: Dear 0x0000000:
Posted: Tue Aug 13, 2013 6:33 am
Holy shit, I just named myself after an error I got on Windows XP when trying to execute my build. (Just kidding, I meant what bbguimaraes said :P)