3 ms·
Without continued development of the language, C will be unable to cope with the needs of modern programming problems and programmers; as a result, it will fade
by jessaustin 9y ago
Without continued development of the language, C will be unable to cope with the needs of modern programming problems and programmers; as a result, it will fade into disuse.
C11 is pretty nice! C99 is too. One might think that "almost once a decade" is kind of slow for updates, but M$ have enough trouble keeping up with the current schedule. Of course TFA describes a possible direction for C2x, but they could have a more charitable attitude...
- nine_k 9y ago> will fade into disuse. That's one thing I'd like C to do. It was an adequate language in 1970, but in 2018, we have a few better approaches that have a chance to turn into viable alternatives to C. Of course, I don't see C falling into disuse any time soon. The amount of critical code written in C is enormous, without a way in sight to reasonably replace. So keeping C in a good shape is important, whatever shortcomings the language may have.
- pjmlp 9y agoNot even that much in 1970, if you look into old papers about the systems programming languages being used at other research institutes besides AT&T.
- Roboprog 9y agoIndeed. Having started my CS degree work in the early 80s, I got to see “things other than C/C++”. In retrospect, I often jokingly refer to the 80s as “the x86/PC disaster”, an extinction level event for programming languages where the choices were to run either assembler, or C, on the IBM PC to build software of any size due to the limitations of the hardware. Rather than trying to improve curly brace languages, it’s time to bury them. For starters, hiding identifiers after arbitrarily long type expressions, instead of starting a line/block/expression with a name, is an un-fixable PITA. (Sorry, AT&T, Algol had it right) Requiring a “break” in a case statement is a botch, instead of some kind of “or” / “set” / “range” test. C is useful as a portable assembler, I guess. Otherwise I don’t really like any of C’s offspring all that much. I sort of like Javascript in spite of being forced to look like Java/C++, but that’s only because I learned some Lisp (alas, not Scheme) back in the day.
- pjmlp 9y agoMicrosoft does not have any trouble keeping up with C, C++ and .NET Native are the future of systems programming on Windows. C compatibility is kept to the extent of ANSI C++ requirements. ANSI C++14 requires C99 library compatibility and ANSI C++17 was updated for C11 library compatibility. http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0063r2.html http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0063r2....
- jessaustin 9y agoThey are improving! Six years is less than fifteen.
- insulanus 9y agoHerb Sutter doesn't like C. That may be the reason that the compiler group at Microsoft don't put any effort into updating the C compiler to support newer features. They do put a great deal of work into the C++ compiler, and seem to be doing a way, way, better job than they were in the late 90s. That may be the other reason they don't update the C compiler with new features.
- pjmlp 9y agoThe reason is official and has been communicated many times. C related improvements will only be done to the extent required by ANSI C++, or requests from key customers that might influence roadmap. Anyone that really deeply wants to keep using C on Windows, and even enjoys using COM directly from C (the main ABI since Windows 7 and UWP core stack), can use any other C compiler. In fact Microsoft has suggested clang multiple times, and has helped clang devs to make it work better on Windows.