Article View: comp.std.unix
Article #307Re: parseargs vs. getopt
From: Chip Salzenberg
Date: Wed, 27 Jun 1990 12:41
Date: Wed, 27 Jun 1990 12:41
19 lines
1101 bytes
1101 bytes
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
Technical Details
Message-ID:
<741@longway.TIC.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!longway!std-unixReferences:
<728@longway.TIC.COM> <729@longway.TIC.COM> <733@longway.TIC.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!longway!std-unix From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.std.unix Subject: Re: parseargs vs. getopt Message-ID: <741@longway.TIC.COM> Date: 27 Jun 90 12:41:55 GMT References: <728@longway.TIC.COM> <729@longway.TIC.COM> <733@longway.TIC.COM> Sender: std-unix@longway.TIC.COM Reply-To: std-unix@uunet.uu.net Organization: ComDev/TCT, Sarasota, FL Lines: 19 Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)