On Sunday 11 May 2008 18:43:57 Andy Lester wrote: > 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 accept that, and the note helps, but I just pulled the conditional declarations out of the block and ran make headerizer again. It put the headers for the conditional functions back in the headerizer block. Is there any hope of convincing the headerizer to ignore these functions without making it effectively a C preprocessor? I'd like to avoid all of: 1) watching commits very closely so that no unpleasant headerizer changes sneak in and break the build on platforms where declaration without definition is more than a warning 2) fixing these changes manually every time they sneak in 3) adding some additional headerizer declaration to these functions to note not to include them If #3 is the best solution however, I can live with it. -- c
