home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
std_unix
/
v20
/
followdir
/
1003.2.f
< prev
next >
Wrap
Internet Message Format
|
1990-08-02
|
1KB
From jsq@tic.com Thu Jun 28 15:39:10 1990
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA08943; Thu, 28 Jun 90 15:39:10 -0400
Posted-Date: 27 Jun 90 12:41:55 GMT
Received: by cs.utexas.edu (5.64/1.65)
id AA13723; Thu, 28 Jun 90 14:39:04 -0500
Received: by longway.tic.com (4.22/tic.1.2)
id AA05245; Thu, 28 Jun 90 12:17:32 cdt
From: Chip Salzenberg <tct!chip@cs.utexas.edu>
Newsgroups: comp.std.unix
Subject: Re: parseargs vs. getopt
Message-Id: <741@longway.TIC.COM>
References: <728@longway.TIC.COM> <729@longway.TIC.COM> <733@longway.TIC.COM>
Sender: std-unix@tic.com
Reply-To: std-unix@uunet.uu.net
Organization: ComDev/TCT, Sarasota, FL
Date: 27 Jun 90 12:41:55 GMT
Apparently-To: std-unix-archive@uunet.uu.net
From: chip@tct.uucp (Chip Salzenberg)
According to darcy@druid.uucp (D'Arcy J.M. Cain):
>[Getarg] support[s] extra functionality which can be used if the user
>is aware of it. For one thing, options and arguments (files) can be
>mixed instead of requiring all options to precede the files.
Consider:
rm ./-a -b -c -d -e -f
With getopt, all five arguments are filenames. With getarg, the first
argument is a filename and the rest are options. This is a feature?
No thanks.
--
Chip Salzenberg at ComDev/TCT <chip@tct.uucp>, <uunet!ateng!tct!chip>
Volume-Number: Volume 20, Number 53