bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Adding strfmon(3) to Gnulib?


From: John Zaitseff
Subject: Re: Adding strfmon(3) to Gnulib?
Date: Sat, 11 Aug 2018 14:31:50 +1000
User-agent: NeoMutt/20170113 (1.7.2)

Hi, all,

I wrote back on 23rd July:

> [...] Is it worth adding strfmon(3) and possibly strfmon_l(3) for
> those systems that do not have it?  I'm thinking primarily
> OpenBSD, even in the latest version.  This OS does not have
> <monetary.h> either.

and

> [...] If the Gnulib maintainers are agreeable, I'll try setting
> aside some time in the next couple of weeks to come up with a
> suitable patch [...]

Just to let you know that I've started work on replacement strfmon
and strfmon_l functions.  My current thinking, before I get too far
into the task, is to:

1. Rename the monetary module to monetary-h and extend it to provide
   an actual replacement for <monetary.h>, a la <glob.h>.

2. Create a strfmon module to provide the strfmon() function.  This
   will depend on monetary-h.  I will almost certainly implement the
   function using GNU C Library (glibc) source code.  I'll look at
   how the glob, getopt-gnu and getopt-posix modules do it... or
   should I be looking at other "model" modules?

3. Rework the existing strfmon_l module to provide a replacement
   strfmon_l() function instead of just working around bugs in old
   versions of glibc.  Again, I'll be using current glibc code.

4. Create a replacement monetary module that depends on monetary-h,
   strfmon and strfmon_l, with a message that monetary is now
   obsolete and that programmers should use strfmon and/or
   strfmon_l.

5. Develop appropriate tests for all of the above.

6. Update documentation in doc/posix-headers and doc/posix-functions
   to suit.

7. Add appropriate lines into MODULES.html.sh and config/srclist.txt.

Anything major I've forgotten?  And yes, I've read Chapter 4 of the
GNU Gnulib manual--in fact, I've read the whole document based on
the current git sources :-)  I expect the patches will need to go
through a few iterations on this mailing list before being merged,
of course.  I've also signed the copyright assignment papers and
sent those off.

Yours truly,

John Zaitseff

-- 
John Zaitseff                    ,--_|\    The ZAP Group
Phone:  +61 2 9643 7737         /      \   Sydney, Australia
E-mail: address@hidden   \_,--._*   http://www.zap.org.au/
                                      v



reply via email to

[Prev in Thread] Current Thread [Next in Thread]