Linked by Thom Holwerda on Fri 13th Jul 2012 23:39 UTC
Thread beginning with comment 526974
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Too many platforms
by moondevil on Mon 16th Jul 2012 08:42
in reply to "RE[6]: Too many platforms"
"No, because those .so won't be able to link with the kernel ABI of today's Linuxes.
I guess, you meant "syscall" ? Since syscalls are considered a private API, a "professional software developer" would not use them, and instead would use the POSIX API that are exposed in the glibc, which keeps backward binary compatibility. "
ABI is much more than just syscalls.
An ABI implies syscalls, calling conventions, memory layout for data structures, executable file formats, ...
Regarding your glibc example, it depends on how your application links with it, assuming it was even compiled with gcc.
Edited 2012-07-16 08:43 UTC




Member since:
2006-02-01
I guess, you meant "syscall" ? Since syscalls are considered a private API, a "professional software developer" would not use them, and instead would use the POSIX API that are exposed in the glibc, which keeps backward binary compatibility.
Any professional software developer that use syscalls directly instead of POSIX should be demoted from its "professional" rank (with a few exceptions being Kernel and libc hackers).
Edited 2012-07-16 07:59 UTC