[PATCH] getopt,argp - reentrant getopt interface, argp fixes

Marcus Brinkmann marcus.brinkmann@ruhr-uni-bochum.de
Sat Mar 6 20:18:00 GMT 2004


At Wed, 3 Mar 2004 14:53:26 -0800,
Roland McGrath wrote:
> 
> > Then the interface is misused this way.  getopt explicitly is not thread
> > safe in POSIX because of its restricted use.
> 
> We are talking about argp here, really.  I hope you won't claim such uses
> were not part of the original intent of argp, because they most certainly
> were.  The reason for changing getopt is to make it a suitable subroutine
> for a cleaned-up argp.  The other alternatives are to make such new entry
> points wholly internal, just to be used by argp, or rewrite argp not to use
> getopt at all.

The attached patch does make the new entry point wholly internal.
It's a replacement for the original three patches.  The same
considerations as in my original mail (except for the discussion of
the external getopt interface of course) still apply.

Thanks,
Marcus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: libc-argp2.diff
Type: application/octet-stream
Size: 44117 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20040306/ee221b59/attachment.obj>
-------------- next part --------------



More information about the Libc-alpha mailing list