4 ms·
Rule 0: don't write safety-critical code in C.
by lisper 10y ago
Rule 0: don't write safety-critical code in C.
- AnimalMuppet 10y agoNice snark, I guess, but... did you actually read the article? One of the reasons for C is that the tooling around it gives you much more support. For safety critical code, you need that, because programmers make mistakes, no matter what the language. So if you write safety critical code in Haskell, say, you won't have a large number of the holes that C gives you. But for safety critical systems, their rules say that you can't write code that has even the possibility of falling into those holes. That makes C much safer. That leaves you with a safer C, plus tooling, vs. Haskell (or whatever your choice is) without the tooling. So, snark aside, what is your actual alternative that you recommend?
- lisper 10y ago> did you actually read the article? Yes. I used to work with the person who wrote it. > One of the reasons for C is that the tooling around it gives you much more support. That's because C is an unsafe language, so to write safe code you need that tooling. If you start with a safe language the need for that tooling simply evaporates because many of the mistakes that the tooling is designed to catch are simply not possible. > For safety critical code, you need that, because programmers make mistakes, no matter what the language. That's certainly true, but many of those mistakes are mistakes in the rendering of the desired semantics into code. Neither rules nor tooling can catch those kinds of mistakes. > But for safety critical systems, their rules say that you can't write code that has even the possibility of falling into those holes. That makes C much safer. No, it doesn't. All of the rules that are not specific to C can be equally well applied to any other language. > So, snark aside, what is your actual alternative that you recommend? Good heavens, just about anything is better than C if what you care about is safety. Ada. Java. Scheme. Haskell. OCaml. Python. Go. Swift. Common Lisp.
- AnimalMuppet 10y agoWell, of those, Java, Haskell, and Lisp (at a minimum) are completely unsuitable due to allocation and, worse, garbage collection. In a hard real-time system those are a deal breaker. (Usually. You can have deterministic allocators and guaranteed-worst-response-time garbage collectors, and then you can still prove you can meet your timing requirements, but it's not easy. Or, you can try to write those languages in a way that they never allocate after initialization, which might be possible, at least for Java.) Python? Can't you get "method not supported" (or whatever the technical term is within Python)? That's not safety, by any stretch of the imagination. Or is there some way to prove that it can't happen, by some kind of (ahem) external tooling? Ada I could accept. Go and Swift might be suitable. I don't know enough about Scheme or OCaml to comment.
- lisper 10y ago> completely unsuitable You are wrong. And you even admit that you are wrong in your own comment: "You can... but it's not easy" There's a big gap between "completely unsuitable" and "not easy." But you are wrong for an even more fundamental reason: the matter at hand is not hard-real-time cade, it is safety-critical code (re-read the title). Those are not the same thing. Safety-critical code can be and has been written in Common Lisp. Moreover, an effort to port the Common Lisp code to C++ failed. So it is manifestly untrue that Common Lisp is "completely unsuitable" for writing safety critical code.
- AnimalMuppet 10y agoThe title says "safety critical code". But the article says no allocations, because of the unpredictable (time) behavior. So the environment that the article describes is safety-critical, and part of that is predictable (guaranteed) timing. > You are wrong. And you even admit that you are wrong in your own comment Do you realize that you're agreeing with me? I put that part in parentheses in for a reason...
- lisper 10y ago> Do you realize that you're agreeing with me? No. I am not agreeing with you. You are wrong about everything, even the real-time part. You are even wrong when you say it's not easy to write hard-real-time code in GC'd languages. It is no harder to do that in GC'd languages than in non-GCd languages. In fact, it's easier. You are correct that it is hard to write a hard-real-time GC. But that job only has to be done once, and it has already been done so at this point it's a sunk cost. Writing non-consing code is also not hard, certainly no harder than writing non-consing code in C. Not only is Common Lisp suitable for writing safety-critical code, it completely dominates C in every possible way. And this is not just speculation, it has been actually demonstrated in the field. Oh: > But the article says no allocations, because of the unpredictable (time) behavior You're wrong about this too. It does say it's because of the unpredictable behavior, but the "time" part is your own extrapolation. The article itself says nothing about hard-real-time. The word "time" does not even appear anywhere. (Not that this matters because it is no harder, and often easier, to write hard-real-time code in Lisp as it is in C.)