2 ms·
Too bad that's a straw man since the comment you replied to didn't say anything about not using pointers and resursion. It said real programmers don't ask that
by dahart 10y ago
Too bad that's a straw man since the comment you replied to didn't say anything about not using pointers and resursion. It said real programmers don't ask that many questions about them.
Also too bad for your high horse answer that all the best real world programmers acknowledge that pointers & recursion are places where bugs hide disproportionately. Many real world programmers suggest that pointers & recursion are things to avoid. NASA's safety code guidelines are well known around here because it says explicitly to avoid both recursion and pointers.
Rule #1: "Restrict all code to very simple control flow constructs – do not use goto statements, setjmp or longjmp constructs, and direct or indirect recursion."
Rule #9: "The use of pointers should be restricted. Specifically, no more than one level of dereferencing is allowed. Pointer dereference operations may not be hidden in macro definitions or inside typedef declarations. Function pointers are not permitted."
https://en.m.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code https://en.m.wikipedia.org/wiki/The_Power_of_10:_Rules_for_D...