Thread: Best safe C programming competitive recommendations for that moment

Hi, guys!
Today we have several C substitutes but C will never die. What could you recommend to read or give just your own practice recommendations to code safe applications in C without common mistakes? I have found this one - Seventeen steps to safer C code - Embedded.com - but someone can improve it himself here.
Thanks.

How can you determine if you have finished the development?

1. There is no more money left;
2. There is no more time left; or
3. All the requirements are implemented and tested successfully.

At my work, it's ALWAYS 2! lol

I find it strange that it didn't mention the standard errno.h header file...

And don't "=0" the first enum element - The standards say if it is not initialised, it becomes = 0. (Every element after that us the previous one +1)