Dear Thomas,
this plugin does not work if files are being created from a (project) wizard. In that case it seems a header guard is applied twice...?!
Works fine here? What exactly is the matter?
...it's gone after updating to trunk. :oops:
The headerguard plugin forces me to use the guard <FILENAME_IN_CAPS>_H_INCLUDED
Is there any way to change this default?
I could not find the script to modify either.
I would like it to be <FILENAME_IN_CAPS>_H
Quote from: styggentorsken on December 11, 2008, 03:44:35 PM
The headerguard plugin forces me to use the guard <FILENAME_IN_CAPS>_H_INCLUDED
No, it doesn't. It uses
HEADER_<64 bit hexadecimal number>. The hexadecimal number is a hash of the full pathname. There are no configuration options to change the output.