Re: cf_parser.c->cf_parser.h

cf_parser is one of the odd things

a) It is not a standalone C file

b) It is not a C header file as it includes code, and not only definitions.

Having it named .c is as appropriate as having it named .h. Neither are
entirely correct or wrong.

In most other cases where I have seen similar constructs, the included code
is named .c to not confuse it with a header file.

--
Henrik
Robert Collins wrote:
> This is the last of my queued file renaming patches. No repository
> renaming is required.
>
> Changelog:
>         * src/Makefile.in: Rename cf_parser.c to cf_parser.h - we never
> build a
> cf_parser.o, so .c isn't really appropriate.
>         * src/cache_cf.c: Ditto.
>         * src/cf_gen.c: Ditto.
>
> Again, any objections?
>
>   ------------------------------------------------------------------------
>                      Name: cfparser.patch
>    cfparser.patch    Type: Plain Text (text/plain)
>                  Encoding: 7bit