Re: [Gperf-bugs] [Debian #194969] gperf: wrong file and line numbers in warning/error messages

[Bruno Haible]

> Although the new version of gperf tries to be helpful by inserting #line
> directives in the output to reflect the actual input source lines of
> keywords, etc., it fails to reset this to reflect portions of the output
> which are generated by gperf. Thus in cases when gperf generates invalid
> code, the file and line numbers reported by the compiler are wrong.
>
> For example:
>
> frametype.gperf:326: warning: useless keyword or type name in empty
> declaration

Thanks for the report. gperf will be changed to not emit invalid code;
but resetting the #line statements will not be done because
  - When no --output option is used, the destination file name is unknown,
  - It would be strange if "gperf --output=filename.c" and
    "gperf > filename.c" generated different code.

Bruno