On 07/12/2021 10:22, Bart wrote:
That might be the case on Unix where where the OS and C are so
intertwined that that you don't know where one ends and the other
begins.
No, /you/ don't know where one ends and the other begins
From another thread:
On 07/12/2021 09:57, David Brown wrote:
On 07/12/2021 10:22, Bart wrote:
That might be the case on Unix where where the OS and C are so
intertwined that that you don't know where one ends and the other
begins.
No, /you/ don't know where one ends and the other begins
I suspect that's true of many of us. It /is/ confusing when:
1. the C standards documents include the standard library, not just C
2. Clib and OS calls are invoked in the same way (flat namespace)
3. compiler and linker are expected to /search/ for referenced files
4. the 'OS calls' aren't really OS calls but wrappers
5. C headers are separate from the modules they describe
6. one C header can bundle declarations for multiple modules and one
module may need the inclusion of multiple headers (AIUI)
IMO that's a bit of a mess. All of those, even if I understand them
correctly (which is far from certain), blur the boundaries between the language, the language's library/ies, and the operating system.
In a new language all of those six problems can be fixed - and should
be, IMO.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 232:37:03 |
Calls: | 6,624 |
Files: | 12,171 |
Messages: | 5,319,537 |