Article View: comp.std.unix
Article #198Re: Standards Update, IEEE 1003.1: System services interface
From: henry
Date: Fri, 06 Apr 1990 17:42
Date: Fri, 06 Apr 1990 17:42
17 lines
1341 bytes
1341 bytes
From: henry@zoo.toronto.edu
>From: peter@ficc.uucp (Peter da Silva)
>What about Eric Allman's "parseargs" (or my modified version), which have
>finally fulfilled the promise of "getopt" to make argument parsing easy?
What about it? I fear it's a bit late and not sufficiently widely used
to make it into POSIX, which is (mostly) supposed to be standardizing
existing practice. [I'm among those who takes a dim view of the explosive
growth of POSIX committees working on standards for subjects we don't
even understand yet.] I suspect it would also be controversial, since
some of us think getopt() does most of what's really needed.
Henry Spencer at U of Toronto Zoology
uunet!attcan!utzoo!henry henry@zoo.toronto.edu
Volume-Number: Volume 19, Number 70
Technical Details
Message-ID:
<640@longway.TIC.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!longway!std-unixReferences:
<621@longway.TIC.COM> <619@longway.TIC.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!longway!std-unix From: henry@zoo.toronto.edu Newsgroups: comp.std.unix Subject: Re: Standards Update, IEEE 1003.1: System services interface Message-ID: <640@longway.TIC.COM> Date: 6 Apr 90 17:42:01 GMT References: <621@longway.TIC.COM> <619@longway.TIC.COM> Sender: std-unix@longway.TIC.COM Reply-To: std-unix@uunet.uu.net Lines: 17 Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)