10 Rules for Writing Safety Critical Code

http://spinroot.com/p10/

1 Restrict to simple control flow constructs.
2 Give all loops a fixed upper-bound.
3 Do not use dynamic memory allocation after initialization.
4 Limit functions to no more than 60 lines of text.
5 Use minimally two assertions per function on average.
6 Declare data objects at the smallest possible level of scope.
7 Check the return value of non-void functions, and check the validity of function parameters.
8 Limit the use of the preprocessor to file inclusion and simple macros.
9 Limit the use of pointers. Use no more than two levels of dereferencing per expression.
10 Compile with all warnings enabled, and use one or more source code analyzers.

>>1 Sounds like Ada

Meh, meh, YES, bullshit, bullhit, bullshit, meh, bullshit, bullshit, bullshit.

>>3
Are you Jewish? Only jews don't like dynamic memory allocation

C-dder is all talk and no action.

>>5
What's with all the anti-Cudder shilling?

>>6
Now you're spewing memes for no good reason.

11 Do not use the C programming language

>>8
What? That will be ruining security industry and hacking. Also, job security is often fixing and improving C/C++ code. Without C/C++ minimum-wage pajeets would be running the show.

Use rust

Dont botherchecking these

>>9

Also, job security is often fixing and improving C/C++ code.

Haskell is a simple and understandable language for normal people like physicists and mathematicians, cleansed of the byte-sodomy, and it makes specially-bred computer programmer-lametards unnecessary. Yes, you've heard that right. Once this language for normal people becomes widespread, the byte-Sparta of warrior programmer faggots tempered by being assfucked with the von Neumann architecture and fucked in the mouth by the applicative order will lose its raison d'etre. What will they do then, these pathetic subhumans who have had everything human washed out from their heads for five years in coding school? The only thing remaining for them will be ceasing their wretched existence.

>>12
Every time you use Haskell, the Jew takes a dump in your soul.

>>13 Its a new copypasta.

>>3

How would you solve this problem?

http://www.openwall.com/lists/musl/2016/10/17/1
http://www.openwall.com/lists/musl/2016/10/17/2
http://www.openwall.com/lists/musl/2016/10/17/3

2016
not having arbitrary-sized buffers

>>15
By making a better API. In the same way gets() is a stupid idea and was replaced with fgets(), let the caller decide how big the buffer needs to be.

>>17
stop being a namefag

>>18
e/g/in /g/ro

>>19
no

21 YEARS OF CHASTITY GET

>>21
Check em

>>22
no