Standards for Reliable and Safe Code

You *do* practice standards for safe and reliable code for mission critical stuff, right Jow Forums?
lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf

If you can't handle this, you may as well go fuck off to Rust.

Attached: 1539649863234.gif (159x146, 168K)

Other urls found in this thread:

deviantart.com/casetermk
twitter.com/SFWRedditImages

milkies

this

Based

Should just use Ada/SPARK instead of the clusterfuck known a ā€œCā€

>You *do* practice standards for safe and reliable code for mission critical stuff, right Jow Forums?
Yes, but certainly not the standard you linked. That standard is aimed at particular types of embedded software, and completely unsuitable for most types of non-embedded mission critical software, as well as even a substantial part of embedded software.

I hope you have not fooled yourself into cargo-cult following of a particular impressive-looking document without considering what use cases it is designed for, OP.

Offer better

why does everyone hate on rust...

What happened to her nipples?

sauce on the those tits

FUCKING PLEASE

did you even read his post, you retard? there's no general "best" standard to follow on every project

>Do not use direct or indirect recursion.

fucking what?

fpbp

Tmnt?

I reversed image searched it and got this:
//deviantart.com/casetermk

a real american hero

Recursion of any kind is just ASKING for stack overflows. You can't risk that on the mars rover

>friendship with malloc ended

>31 Rules for Life
>JPL's antidote to segfaults

Attached: gaming laptop powerpoint.png (1920x1080, 870K)

No, I use logic to prove that my program works without worrying about that superficial stuff.

they can't go with the times

MOMMY PWEASE GIB MILKIES