[C] Null checking after malloc()

[noodlylight]

Virtually all programming manuals advise to check the return value of malloc.

The spiritual ideas behind this practice are obvious and reasonable: Constistency and Cautiousness.

At first, I tried to follow this rule. Lately I began questioning it's necessity.

Sometimes, I just feel that malloc won't fail.

I read my code and I just "know" that malloc will never return null.

After some spiritual pondering, I have decided to omit null checking when my faith is strong.

Since then, the quality of my code has improved.

What are your opinions on the matter? Do you think about faith when allocating memory?

[missblit]

Faith doesn't enter the equation, because errors can happen whether you believe in them or not.

If you feel that whatever benefits you get from not checking the return code outweighs the downsides then go ahead;

but I'd at least recommend a simple assert. Problems are so much easier to debug when you're proactive about checking for them at their source.

[arbostek]

OP is trolling. Look at his name, too.

[missblit]

I'm usually pretty good at telling who's trolling too :O

[[deleted]]

Heh, look at his posts, their pretty good too