Re: *.m4 conventions

[Bruno Haible]

Paul Eggert wrote:
> Although that's true for experts, it's not necessarily true for 
> beginners who are the main audience for the first line. A beginner won't 
> know whether stdio_h.m4 is for the entire stdio module, or just for 
> configuring the stdio.h replacement, or just for configuring the stdio 
> implementation, or something else.
> 
> In general the first line could be quite helpful for a brief explanation 
> of file contents, for non experts. Yes, this information can be put 
> elsewhere in the .m4 file, but the first line is a better place for it.

I have nothing against adding these brief explanations as a second line:

  # stdio_h.m4
  # Autoconf macros for the stdio module.
  # serial 42

or even in the first line:

  # stdio_h.m4 - Autoconf macros for the stdio module.
  # serial 42

This would satisfy my concerns as well as yours, I think?

Bruno