(likewise for the next line) where {0} is filled in with the header filename. For typical header filenames, this creates preprocessor tokens that look like cheddar_generated_filename.h_h, but . is not a legal preprocessor identifier character (clang under OS X gives a warning about "extra tokens following an identifier", pointing to the .).
Thanks for letting me know, that should be fixed now and I've done a v0.3.1 release for you. Could you check that it has worked then close this issue if it has please.
The ifdef guard is currently defined as
(likewise for the next line) where
{0}
is filled in with the header filename. For typical header filenames, this creates preprocessor tokens that look likecheddar_generated_filename.h_h
, but.
is not a legal preprocessor identifier character (clang under OS X gives a warning about "extra tokens following an identifier", pointing to the.
).