3 ms·
> No, I have seen many people use an arbitrary value Have you seen that in something that's ABI-critical, though? i.e. whose code simply cannot be changed due
by dataflow 2y ago
> No, I have seen many people use an arbitrary value
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.
- AshamedCaptain 2y agoEverything is an ABI issue. Dunno what the point or alternative is here.
- dataflow 2y agoNo? Not every struct is exposed to clients who can't change their code.
- AshamedCaptain 2y agoI 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'.