Re: errno --> errno name ?

[Bruce Korb]

Hi Bruno,

On 08/14/11 10:25, Bruno Haible wrote:
> By the way, instead of defining a macro ERRNO_DISPLAY_FMT (that ends with
> a newline - why?), it is more general to define a macro
>    #define MAX_ERROR_NAME_LENGTH 15
> Users who want to user columns can then do things like
>    printf ("%.*s", MAX_ERROR_NAME_LENGTH + 1, ...)

"%-.*s", no?  Anyway, that is better.  There's enough to printf
that even after all these years, it isn't all at the tips of my fingers....:)
Maybe it's *because* of all the years, I learned it in a predecessor
form and haven't gone back to learn all of what featuritis did to it. :-D

> > Please feel free to tweak it.  I think that might be easier than
> > seeing if I get exactly what you mean, retrying and cycling again.
>
> But through this process of proposing, retrying, and listening to comments

Sure.  It depends somewhat on your (and others') patience, too.
This is kind-of a play time activity.  My focus this weekend is
actually deferred tax returns (due Monday night because I had
this employer who misrepresented my earnings and .....)
The next two weekends are booked, then I go to Europe for a couple
of weeks and when I get back I suspect there will be some chores
around the house.  In other words, it might be a bit like the
libposix stuff.  With another hand, it goes faster.

> It will not find the mk-err-names.sh script in the first place. The Makefile
> rules are executed in the build directory.

OK, the invocation has to have a "where is it?" search.

> Please, that's part of submitting a gnulib module: adding it to your
> gnulib working directory, doing "./gnulib-tool --create-testdir ..." of it,
> and optionally testing this testdir with "mkdir b; cd b; ../configure; make".

Whenever I have both time and inclination (a roundtuit).  Maybe this fall,
unless someone out there wants to play, too.

Cheers - Bruce