4 ms·
> My position is that this is less of a burden than writing something that goes from the "glorious language" into machine code. It's only less of a burden if y
by aidenn0 5y ago
> My position is that this is less of a burden than writing something that goes from the "glorious language" into machine code.
It's only less of a burden if you're guaranteed to have a C compiler hanging around any time the C ABI breaks. If you aren't guaranteed to have a C compiler hanging around any time the C ABI breaks, then you are probably just as well off generating C-ABI compatible machine code from an ABI description written in "glorious language" and updating it when the C ABI breaks.
Non self-hosting languages distributed as source code can just lean on the C compiler for everything.
It's also quite feasible to target Linux without worrying about the C ABI, as the Linux system call interface is famously stable, but that is not true of any BSD.