Printable View
I don't know but it looks like it takes some time to become second nature. knowing that 0101 is 5 can be done easily. but when you have a whole 32 digit binary number it gets a bit hard locating the bits you want.
What I mean is that from Hex to Binary you can get used to it. but the opposite can be very complicating
Yes, and telling the difference between a 1 with 30 zeros and a 1 with 31 zeros can only be resolved by counting them [unless the numbers are right next to each other]. The difference between 0x40000000 and 0x80000000 is pretty immediately noticable.
--
Mats
Theres an 0b prefix in the GNU C language extensions.
Real "structured assembly":Quote:
Originally Posted by matsp
Such a thing can be useful.Code:[p1] = 00010000B ;initalize port before setting direction
[pd1] = 00011110B
; +||||||| I CELL_MOD_ON_STATE/INT (int5l)
; |+|||||| I RF2400_STATUS/INT (int4l, pullup)
; ||+||||| I EBRD_INT (int3l, pullup)
; |||+|||| OH SERIAL_FLASH_CS (low true)
; ||||+||| OL RAW_SW_ENA (also enable 5v, hi true)
; |||||+|| OL BATT_CHARGE (hi true, set BATT_LOAD=0 first!!)
; ||||||+| OL BATT_LOAD (hi true, set BATT_CHARGE=0 first!!)
; |||||||+ I PHONE_LINE_DET
If you don't write numbers out in binary then you don't have this problem.Quote:
Originally Posted by Abda92
Can you explain what this line does? It doesn't seem to match the comments, as this would set both BATT_CHARGE and BATT_LOAD.Code:> [pd1] = 00011110B
Port value setting is followed by port direction setting.Quote:
Originally Posted by swoopy
Every one has an opinion on such topics so I guess I'd like to also give mine.
binary is a base 2 alphabet that's been over extended in various ways to cater for much more complexity. I'm of the opinion that it's better left out or left to you the programmer to manipulate the machine language as you see fit. Octal and hex are extended binary with increased base to handle several real world complexities. why have binary notation when you may as well just use assembly notation to show you wish to work with native machine code ( asm )? also think word boundaries and the like. I believe, rather than worry about havein binary notation we should be looking at creating base32 and 64 notations so that we can startd doing more with one letter.
Imagine dealing with huge numberes in base two? (not fun for the mind)
Ok, it took me a while to interpret. I believe I understand. You are referring to this:Quote:
Originally Posted by Dave_Sinkula
Code:I
I
I
O
O
O
O
I
I think the b notation (101101b) deserves to become a standard, just like 0x. I probably wouldn't use it very often; but I'm sure I'd find it handy every now & then.
As for bit flags, these are all the numbers you need to "memorize":
0x1
0x2
0x4
0x8
All flags larger than that are just shifted to the left:
0x10, 0x20, 0x40, 0x80, 0x100, 0x200, 0x400, 0x800...
Aye. Just a random C&P.Quote:
Originally Posted by swoopy