Thank you for your feedback, I will amend my entry. > "Make functions, not procedures" --> "Don't check for errors. Don't even make it possible to check for er

Thank you for your feedback, I will amend my entry. > "Make functions, not procedures" --> "Don't check for errors. Don't even make it possible to check for errors." I will make my tutorial clearer on this point: errors can be embeded in results. Option types can do wonders. Of course, this is not easy to do in C. My opinion is that programming in C means either dealing with legacy code, seeking utmost performance, or being nuts. I think that leaves plenty of room for reasonable programming. I never said that my assertion is valid in all circumstances. Actually I agree with you here. But I would be extremely surprised if my advice couldn't be followed by most programmers, most of the time.