Why no uint16_t in in6_addr?
| Newsgroups | gmane.network.ipv6.general |
|---|---|
| Message-ID | <[email protected]> |
In RFC 3493, it says:
struct in6_addr {
union {
uint8_t _S6_u8[16];
uint32_t _S6_u32[4];
uint64_t _S6_u64[2];
} _S6_un;
Why is it not:
struct in6_addr {
union {
uint8_t _S6_u8[16];
uint16_t _S6_u16[8];
uint32_t _S6_u32[4];
uint64_t _S6_u64[2];
} _S6_un;
Adding the uint16_t breakdown seems like it would be useful, and cost
nothing. Is there some non-obvious reason it was left out?
Roy Smith <[email protected]>
Staff SW Engineer
EMC / Smarts
+1 914 580 3427
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [email protected]