Re: cvs commit: libh/util check_guards

I'm not sure I understand what this script does.

Does it force a given file.hh to have header guards like:

#ifndef FILE_HH
#define FILE_HH
/* c code here */
#endif

in other words, what is the format of the XXXX in your commit log?

I'm not sure that an additional md5 suffix is necessary. There
shouldn't be similar header file names. Anyways, with the compile dir
scheme if there's files with identical file names, they're going to
make a mess in the compile directories.

A.

On Sat May 04, 2002 at 03:01:23AM -0500, Max Okumoto wrote:
> okumoto     2002/05/04 03:01:23 CDT
> 
>   Added files:
>     util                 check_guards 
>   Log:
>   This script validates header guards.  The file must begin and end
>   with the guards, with matching tags.  If they are found and the
>   tags all match a new tag is generated from the basename of the
>   header file.  An additional md5 suffix, generated from the path
>   to the file, is appended to differentiate this file from any other
>   file with the same name.
>   
>   #ifndef XXXX
>   #define XXXX
>   /* c code here */
>   #endif XXXX
> 
> 
> To Unsubscribe: send mail to [email protected]
> with "unsubscribe freebsd-libh" in the body of the message


-- 
Why bother building more nukes until we use the ones we already have?

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

iEYEARECAAYFAjzV5wIACgkQttcWHAnWiGeMGgCeMXsmZa0BQlNO/6IsdTMa1W5Q
me8An0haV4iiu0l785Lk/1XdMLNvtXO7
=jY78
-----END PGP SIGNATURE-----