5 ms·

Don't fix what's not broken.

• theoh 10y ago
  I apologize in advance but... "necessity"... Surely not THE "necessity", mother of invention? I guess that would absolutely give you a veto on other people "scratching their own itches". Snark aside, the issue is surely whether, if designing C now, the last 40 years of programming language theory would not have some impact.
• adamnemecek 10y ago
  C isn't broken?
  • necessity 10y ago
    Why would you think it is?
    • adamnemecek 10y ago
      Not memory safe, bad type system, terrible 'macro' system, no/minimal(C11) support for generics, minimal standard library, pretty verbose (it's hard to build any good abstractions), lack of functional programming support, undefined behavior. Dealing with dependencies and headers in any but the simplest of projects gets old really quickly. Just about bigger project I've seen abuses the language to some extent. The list goes on and on.
• wolf550e 10y ago
  Basically every deployed C codebase contains "undefined behavior".
  • necessity 10y ago
    Which is intended. Suggested reading: http://blog.regehr.org/archives/213 http://blog.regehr.org/archives/213
    • majewsky 10y ago
      But I will still always argue that it's a bad trade-off to make compiler construction slightly easier at the expense of insecure code all over the place.