Re:The trouble with struct sockaddr's fake flexible array
by AshamedCaptain on Friday November 29, 2024 @10:33AM
(#42274519)
Everything is an ABI issue. Dunno what the point or alternative is here.
Re:The trouble with struct sockaddr's fake flexible array
by dataflow on Friday November 29, 2024 @10:35AM
(#42274529)
No? Not every struct is exposed to clients who can't change their code.
Re:The trouble with struct sockaddr's fake flexible array
by AshamedCaptain on Friday November 29, 2024 @01:19PM
(#42275818)
I still do not see the point. No one wants to change their code. No one wants to break their ABI. But the discussion is moot since I do not see what ABI break is being proposed here. My only guess is that the proposal you're envisioning is to forbid this pattern, which breaks a lot of perfectly working code, not just 'ABI'.
Have you seen that in something that's ABI-critical, though? i.e. whose code simply cannot be changed due to backward compatibility, like is the case with sockaddr? Because otherwise I'd consider it a non-issue.