Re: [PATCH 1/4] stdbit: new module

[Collin Funk]

On 5/12/24 8:23 AM, Paul Eggert wrote:
> Is this stuff documented somewhere in the .texi files? If not, I suppose it 
> should be.

I'm not sure. The only reason I noticed was because I was working on
endian.h and using stdbit as a template since my m4 talents are lacking...

> Frankly I continue to be annoyed by having to read and write a line "# 
> FILENAME.m4" at the start of every m4 file FILENAME.m4. It's better for a 
> file's first line to be a human-readable comment explaining what the file is 
> for. Any automated procedure already knows the file name, so why do we need 
> to put the name there manually, an error-prone process?

I have similar feelings about some stuff in gnulib-tool.py. We have
lines like this:

#========================
# Define GLImport class
#========================
class GLImport:
      ....

But when searching for a class in Python you can simply look up
'^class NAME:' since whitespace matters in that language. No need for
the comment in my opinion.

Collin