#bitfields — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #bitfields, aggregated by home.social.
-
“Bitfield Pitfalls”, Michal Necasek, OS/2 Museum (https://www.os2museum.com/wp/bitfield-pitfalls/).
Via HN: https://news.ycombinator.com/item?id=47469945
On Lobsters: https://lobste.rs/s/xtue97/bitfield_pitfalls
#C #Programming #BitFields #Gotchas #C89 #C11 #Bits #SystemsProgramming #Compilers
-
“Bitfield Pitfalls”, Michal Necasek, OS/2 Museum (https://www.os2museum.com/wp/bitfield-pitfalls/).
Via HN: https://news.ycombinator.com/item?id=47469945
On Lobsters: https://lobste.rs/s/xtue97/bitfield_pitfalls
#C #Programming #BitFields #Gotchas #C89 #C11 #Bits #SystemsProgramming #Compilers
-
“Bitfield Pitfalls”, Michal Necasek, OS/2 Museum (https://www.os2museum.com/wp/bitfield-pitfalls/).
Via HN: https://news.ycombinator.com/item?id=47469945
On Lobsters: https://lobste.rs/s/xtue97/bitfield_pitfalls
#C #Programming #BitFields #Gotchas #C89 #C11 #Bits #SystemsProgramming #Compilers
-
“Bitfield Pitfalls”, Michal Necasek, OS/2 Museum (https://www.os2museum.com/wp/bitfield-pitfalls/).
Via HN: https://news.ycombinator.com/item?id=47469945
On Lobsters: https://lobste.rs/s/xtue97/bitfield_pitfalls
#C #Programming #BitFields #Gotchas #C89 #C11 #Bits #SystemsProgramming #Compilers
-
Bit Fields trong C: Giúp tiết kiệm bộ nhớ bằng cách đóng gói bit trong struct, nhưng bố cục phụ thuộc trình biên dịch → Không đảm bảo tính di động.
Tuyệt đối không dùng cho thanh ghi phần cứng! Ưu tiên:
• Bit Fields: cờ nội bộ, state machine (dễ đọc, nhóm cờ)
• Bit Mask: phần cứng/giao thức (kiểm soát bit chính xác)
#LậpTrìnhC #BitFields #EmbeddedSystems #Programming #ViMạch #Chttps://dev.to/amanprasad/bit-fields-in-c-explained-how-they-work-and-why-they-matter-34i9
-
@bug a u2; or an s2, if it's signed.
A byte is a u8, a nibble :blobcatcookienom: is a u4.
A a dword is a u32 and a qword is a u64... and so on.
Simple, unambiguous, and it even tells you whether it's signed or unsigned... but it's not cute :blobfoxboopcute:, I grant you.
I think it's unlikely to be confused with the high-altitude plane ✈️ or the rock band :blobcatcool:, given context 😁
-
@bug a u2; or an s2, if it's signed.
A byte is a u8, a nibble :blobcatcookienom: is a u4.
A a dword is a u32 and a qword is a u64... and so on.
Simple, unambiguous, and it even tells you whether it's signed or unsigned... but it's not cute :blobfoxboopcute:, I grant you.
I think it's unlikely to be confused with the high-altitude plane ✈️ or the rock band :blobcatcool:, given context 😁
-
@bug a u2; or an s2, if it's signed.
A byte is a u8, a nibble :blobcatcookienom: is a u4.
A a dword is a u32 and a qword is a u64... and so on.
Simple, unambiguous, and it even tells you whether it's signed or unsigned... but it's not cute :blobfoxboopcute:, I grant you.
I think it's unlikely to be confused with the high-altitude plane ✈️ or the rock band :blobcatcool:, given context 😁
-
@bug a u2; or an s2, if it's signed.
A byte is a u8, a nibble :blobcatcookienom: is a u4.
A a dword is a u32 and a qword is a u64... and so on.
Simple, unambiguous, and it even tells you whether it's signed or unsigned... but it's not cute :blobfoxboopcute:, I grant you.
I think it's unlikely to be confused with the high-altitude plane ✈️ or the rock band :blobcatcool:, given context 😁
-
@bug a u2; or an s2, if it's signed.
A byte is a u8, a nibble :blobcatcookienom: is a u4.
A a dword is a u32 and a qword is a u64... and so on.
Simple, unambiguous, and it even tells you whether it's signed or unsigned... but it's not cute :blobfoxboopcute:, I grant you.
I think it's unlikely to be confused with the high-altitude plane ✈️ or the rock band :blobcatcool:, given context 😁