Return to Answer

This answer has been rewritten since the downvote.

I learned from and upvoted @FDS's answer here, because it is good and correct. But, here's a form I find easier to read and understand.

I learned from and upvoted @FDS's answer here, because it is good and correct. But, here's a form I find easier to read and understand.

Related

1. My answer on How to wait in bash for several subprocesses to finish, and return exit code !=0 when any subprocess ends with code !=0?

I learned from and upvoted @FDS's answer here, because it is good and correct. But, here's a form I find easier to read and understand.

// The way preferred by pedantic people who don't want to "be redundant" with // an "unnecessary" `== NULL` check: if (!some_ptr) { printf("ERROR: NULL ptr.\n"); return; } // Versus the more-readable and understandable way which I prefer to use // whenever my peers will approve it without a fight or long argument if (some_ptr == NULL) { printf("ERROR: NULL ptr.\n"); return; } // Note: I just want to get my code merged and move on with life, so if they // won't easily approve my preferred version above, I'll switch to the other, // more-pedantic version of code to try to get a quick approval so I can be // more productive. // There are few things more discouraging than being blocked over // silly "pedantry" when your code is correct, bug-free, well-written, and does // what it says it does. 

This answer has been rewritten since the downvote.

I learned from and upvoted @FDS's answer here, because it is good and correct. But, here's a form I find easier to read and understand.

// The way preferred by pedantic people who don't want to "be redundant" with // an "unnecessary" `== NULL` check: if (!some_ptr) { printf("ERROR: null ptr.\n"); return; } // Versus the more-readable and understandable way which I prefer to use // whenever my peers will approve it without a fight or long argument if (some_ptr == NULL) // in C // if (some_ptr == nullptr) // in C++ { printf("ERROR: null ptr.\n"); return; } // Note: I just want to get my code merged and move on with life, so if they // won't easily approve my preferred version above, I'll switch to the other, // more-pedantic version of code to try to get a quick approval so I can be // more productive. // There are few things more discouraging than being blocked over // silly "pedantry" when your code is correct, bug-free, well-written, and does // what it says it does.