Linked by Thom Holwerda on Fri 13th Jul 2012 23:39 UTC
Thread beginning with comment 526976
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.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-08
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