3 ms·
I can't tell whether the author doesn't know, or is pretending to have no idea, that most systems do not offer a stable system call ABI. Windows is the most ob
by tialaramex 3y ago
I can't tell whether the author doesn't know, or is pretending to have no idea, that most systems do not offer a stable system call ABI.
Windows is the most obvious example. Microsoft does not officially document most of their system calls, and makes no promises that they work how you think they do/ how your unofficial documentation claims they do, or that what worked yesterday will keep working, the official documented APIs are to userspace code that you didn't write.
But this is also common on the other Unix systems besides Linux. You define the libc API as what you're promising and then you deliver or don't deliver features in your syscall ABI and the libc handles the slack.