Hi Jim, > >> m4/group-member.m4 > >> lib/group-member.c > >> lib/group-member.h > >> modules/group-member > >> > >> ... Do you find those confusing? > > > > Somewhat, yes. > > Surely you're exaggerating -- for the sake of argument?
The confusion is not big. But here's where I would put dashes and where I would put underscore's if I had complete freedom: Underscores to reflect a C function name, and dashes to join different semantic levels into a file name. Because of the C function name: getlogin_r.c ok gai_strerror.c ok inet_ntop.c ok acl_entries.c ok iconv_open-aix.gperf ok, it's about iconv_open, not iconv size_max.h ok, it's about SIZE_MAX gl_array_oset.h ok, defines gl_array_oset_implementation Different semantic levels: regex_internal.c -> regex-internal.c fnmatch_loop.c -> fnmatch-loop.c getopt_.h -> getopt.in.h or getopt-in.h Bruno
