Discussion:
minus versus underscore in new getopt file names
Paul Eggert
2017-04-08 09:42:07 UTC
Permalink
Now that I think about it, the longstanding Gnulib and GNU tradition is to use
minus in file names rather than underscore. How about if we rename the
newly-introduced getopt source files to use minus instead of underscore?
Zack Weinberg
2017-04-08 15:15:28 UTC
Permalink
Post by Paul Eggert
Now that I think about it, the longstanding Gnulib and GNU tradition is to
use minus in file names rather than underscore. How about if we rename the
newly-introduced getopt source files to use minus instead of underscore?
I don't think glibc would have any objection to that. I was being
consistent with the existing getopt_int.h - maybe that should be
renamed too?

zw
Paul Eggert
2017-04-09 08:06:40 UTC
Permalink
Post by Zack Weinberg
I was being
consistent with the existing getopt_int.h - maybe that should be
renamed too?
Maybe, but let's defer that as it's a separable change and it's to a
longstanding file name. For now I just renamed the new files, using the attached
Gnulib patch.
Zack Weinberg
2017-04-10 00:16:55 UTC
Permalink
Post by Paul Eggert
Post by Zack Weinberg
I was being
consistent with the existing getopt_int.h - maybe that should be
renamed too?
Maybe, but let's defer that as it's a separable change and it's to a
longstanding file name. For now I just renamed the new files, using the
attached Gnulib patch.
Do you think you could come up with matching patches for glibc? For
this, and for the __nonnull thing. I'm not going to have time this
week.

zw
Paul Eggert
2017-04-10 03:32:35 UTC
Permalink
Post by Zack Weinberg
Do you think you could come up with matching patches for glibc? For
this, and for the __nonnull thing. I'm not going to have time this
week.
I could, but I was sort of hoping that you could handle the glibc side while I
did the gnulib side. :-) There's no rush.

Loading...