Anonymous
10/18/2025, 7:09:51 AM
No.106926440
>>106918897
1. I agree that goto obfuscates code execution paths, however I don't think recursion is "complex", so I'd allow recursion - Recursion can be extremely useful and sometimes it offers the most natural way to solve a certain problem.
2. I agree, infinite loops mean the program halts and cannot do anything unless the loop causes it to run out of memory / crash and that is not ideal either even if the program autorestarts itself
3. Not sure what initialization means here, I agree it could be avoided but sometimes you have to heap-allocate deep struct members individually if that's what it means
4. I agree functions should be kept as simple as possible, but no forceful splitting into multiple functions should be done however
5. Runtime assertions are great for debug builds, I assume their assertions are only present in debug builds.... I agree!
6. Unnecessary scope is always bad because it leads to increased complexity and dependencies, I agree.
7. I agree.
8. I agree, preprocessor should not be abused, that leads to obfuscation
9. I agree, I don't remember when I had to do multi-dereference, probably never - Function pointers are fucked because they can be null or point to invalid addresses, I agree they should be avoided. Faggots like to do "OOP" in C with function pointers, I don't see the point in that! You can't even get smart pointers in C because there is no destruction mechanism (function) for stack objects so I don't see point in OOP in C!
10 I agree, I always use Wall and address sanitizer and such tools in debug mode.
1. I agree that goto obfuscates code execution paths, however I don't think recursion is "complex", so I'd allow recursion - Recursion can be extremely useful and sometimes it offers the most natural way to solve a certain problem.
2. I agree, infinite loops mean the program halts and cannot do anything unless the loop causes it to run out of memory / crash and that is not ideal either even if the program autorestarts itself
3. Not sure what initialization means here, I agree it could be avoided but sometimes you have to heap-allocate deep struct members individually if that's what it means
4. I agree functions should be kept as simple as possible, but no forceful splitting into multiple functions should be done however
5. Runtime assertions are great for debug builds, I assume their assertions are only present in debug builds.... I agree!
6. Unnecessary scope is always bad because it leads to increased complexity and dependencies, I agree.
7. I agree.
8. I agree, preprocessor should not be abused, that leads to obfuscation
9. I agree, I don't remember when I had to do multi-dereference, probably never - Function pointers are fucked because they can be null or point to invalid addresses, I agree they should be avoided. Faggots like to do "OOP" in C with function pointers, I don't see the point in that! You can't even get smart pointers in C because there is no destruction mechanism (function) for stack objects so I don't see point in OOP in C!
10 I agree, I always use Wall and address sanitizer and such tools in debug mode.