It's not really the struct sockaddr sa_data[14] problem, it's still a compiler problem - treating explicitly sized buffers at the end of structs to be not expli

It's not really the struct sockaddr sa_data[14] problem, it's still a compiler problem - treating explicitly sized buffers at the end of structs to be not explicitly sized. It's a compiler bug. 14 bytes is 14 bytes, and [1] is one byte not a many or some. And the API's should follow. For the folks who need more bytes, invent your own type. Or set socket attributes as everyone else.