On Sunday 11 May 2008 18:43:57 Andy Lester wrote: > On May 11, 2008, at 4:09 PM, chromatic wrote: > > headerizer should *not* delete preprocessor directives. What needs > > changing so that it doesn't mangle this code in the future? > > A massive reworking of how headerizer handles header files, because > what you expected here is not at all how the headerizer works. > > The sections that the headerizer rewrites are not for human > modification. Putting preprocessor directives between HEADERIZER > BEGIN and HEADERIZER END is the same as modifying an auto-generated > file. As the headerizer exists now, you have no expectations of > having your changes continue to exist.
I'm trying to decide which I hate more, headerizer, C, or #ifdefs in .c files. Ah, who am I kidding? It's the latter. If you add a note to headerizer to this effect (or tell me "It's already there, you dope!") I'll fix the .c files so this won't happen again. -- c
