Linked by Kroc Camen on Mon 30th May 2011 06:37 UTC
Thread beginning with comment 475096
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.
Breaking the binary system call interface, in the case of Linux. Like, I don't know, giving a new parameter to malloc that is mandatory and has no default value. Or switching the integer type used to store PIDs from 32-bit to 64-bit, it that's not done already.
Edited 2011-05-30 14:55 UTC
That's why people should use libc and use the ANSI C and Single UNIX Specification standards. If you use syscalls you ought to get bitten in the tail.
By the way, the kernel does not have a malloc system call, it is implemented as a C library function. The C library normally manages the heap, and grows the heap if necessary with the brk() (or depending on the implementation/situation mmap()) system call.
Edited 2011-05-30 16:33 UTC






Member since:
2007-07-27
What do you mean with massive breaking API changes? Care to elaborate?