standards for include guards?

Sam TH sam@uchicago.edu
Thu May 17 07:43:00 GMT 2001


Without getting into a discussion on the merits of include guards in
GCC, is there some standard for naming such guards?  With the help of
grep, I have found:

 _FILENAME_EXT
 GCC_FILENAME_EXT
 __GCC_FILENAME_EXT__
 _GCC_FILENAME_EXT
 __FILENAME_EXT__
 __filename_ext
 FILENAME_EXT_INCLUDED
 FILENAME_EXT
 _FILENAME_EXT_
 JV_FILENAME_EXT (in java/)
 _DIR_FILENAME_EXT
 _H_f_filename (in f/)
  
Then, the weird ones:
java/parse.h: JV_LANG_H 
gstab.h: __GNU_STAB__
glimits.h: __LIMITS_H_

Maybe something should be picked?
           
sam th --- sam@uchicago.edu --- http://www.abisource.com/~sam/
OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key
DeCSS: http://samth.dynds.org/decss

-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7A+dGt+kM0Mq9M/wRAt1EAJ4haEtZaamxZYaXlLzHra8iFv/DlgCfacdI
xwj+2EJxzALt1CMInPjQpbM=
=5j+T
-----END PGP SIGNATURE-----


More information about the Gcc mailing list