coding style - best-practice on C header files with #ifndef #define #endif

Question

what is concerned best practice regarding the following "pattern"?

#ifndef BLAFOO_H
#define BLAFOO_H
/* ...
 * ...
 */
#endif /* BLAFOO_H */

how should i name the header in the #define directive? i've seen all from said BLAFOO_H to __BLAFOO_H to _BLAFOO_H_ etc..

Answer 1

Name them BLAFOO_H (personnally I use BLAFOO_H_ where BLAFOO is the header file name ).

Make sure your BLAFOO doesn't clash with other files/libraries/etc. you're using, e.g. have your project and/or module name be parth of that name.

Identifiers starting with a _ is reserved for the implementation/compiler, so don't use that.