Fact is there are many examples of operating systems implemented with GC enabled systems languages.
Spin, Oberon, Singularity, Home are just a few of them.
The main problem is that for a systems programing language to be used a such, there much exist a successful operating system that uses it as its main language.
In Windows 8, the main systems language is C++/CX (C++ with reference counting extensions), so the time will come.
The fact that many compilers will warn with '-Wall' about code which is clearly incorrect, but due to the rules of C they cannot simply reject, is irritating.
The rules of C are actually stricter than many reople realize (add -std=c99 -pedantic-errors to gcc and you can get an idea about that -- this, however, still won't catch semantic errors like aliasing violations).
Personally, I'm using clang with -Weverything and remove warnings as necessary. On gcc, there are a lot of useful warnings which are not included in -Wall. My current warning levels look like this:
-std=c99 -pedantic -Werror -Wall -Wextra \
-Wmissing-prototypes -Wmissing-declarations -Wshadow -Wpointer-arith \
-Wcast-align -Wwrite-strings -Wredundant-decls -Wcast-qual \
-Wnested-externs -Winline -Wno-long-long -Wconversion -Wstrict-prototypes
Re:Why Systems Programmers Still Use C (2006)
by queensnake on Monday March 19, 2012 @01:48AM
(#3722559)
(add -Werror - your students will never know.)
I teach C, and I would love a "cleaner C" mode, which just got rid of lots of the bizareeness of C, several of which you mention. The fact that many compilers will warn with '-Wall' about code which is clearly incorrect, but due to the rules of C they cannot simply reject, is irritating.