- #1
RedX
- 970
- 3
Is it true that the the makers of the programming language C get to specify standards for runtime libraries, and operating manufacturers must implement those standards in the runtime libraries they provide for C?
Or do the operating system manufacturers tell the makers of C "here are my system calls to access the kernel, and you, the makers of C, have to write a runtime library using these system calls"?
Say I wanted to write my own high-level programming language for an x86 architecture. I create my preprocessor, compiler, and linker, and I assume that operating system manufacturers won't write the runtime libraries for me like they do for C. Therefore I am stuck writing runtime libraries using system calls that were optimized for use with C?
Or do the operating system manufacturers tell the makers of C "here are my system calls to access the kernel, and you, the makers of C, have to write a runtime library using these system calls"?
Say I wanted to write my own high-level programming language for an x86 architecture. I create my preprocessor, compiler, and linker, and I assume that operating system manufacturers won't write the runtime libraries for me like they do for C. Therefore I am stuck writing runtime libraries using system calls that were optimized for use with C?