2 ms·
Except it did. Multiple times. And I vaguely recall one incident where they couldn’t revert although maybe I’m misremembering. > The Linux ABI definition is bo
by vlovich123 4y ago
Except it did. Multiple times. And I vaguely recall one incident where they couldn’t revert although maybe I’m misremembering.
> The Linux ABI definition is both fuzzy and controversial. Some ABI breaks are unavoidable. [1]
[1] http://she-devel.com/Chaiken_LinuxABI.pdf http://she-devel.com/Chaiken_LinuxABI.pdf
Ultimately it sounds like the policy is actually 0 “reallly bad ABI breaks” where “bad” is a subjective evaluation of how many bug reports they get or breaking something foundational (eg pulse audio). It’s just not possible to freeze the ABI because people may have found kernel bugs and worked around them and the fix for the kernel bug breaks the workaround. That’s what Hyrum’s law means and the Linux kernel doesn’t have a unique solution here. Don’t get me wrong. They do a fantastic job all things considered. But the “never break ABI” is more marketing than a hard and fast rule (but yes they generally get as close as is feasible to sticking to it)
- SAI_Peregrinus 4y agoABI ≠ API. The ABI is a property of the program, the compiler (including options used during compilation), and the target platform. Semver only concerns itself with API, ABI isn't even a consideration there.
- vlovich123 4y agoI doubt many practitioners of semver would agree that changing the behavior of a function in a breaking way would technically be a ok because it only covers the API signature. Semantic versioning frequently means “non-major version is ok to blindly update and not only will the code still compile it’ll also behave the same way at runtime”, branding notwithstanding. “Public api never breaks” as OP posted, for example, is a reference to the Linux ABI policy