Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site mcc-db.UUCP
Path: utzoo!decvax!genrad!panda!talcott!harvard!seismo!ut-sally!mcc-db!jbc
From: jbc@mcc-db.UUCP (John B. Chambers)
Newsgroups: mod.std.unix
Subject: getopt bundling brouhaha
Message-ID: <248@mcc-db.UUCP>
Date: Sun, 14-Jul-85 19:56:32 EDT
Article-I.D.: mcc-db.248
Posted: Sun Jul 14 19:56:32 1985
Date-Received: Mon, 15-Jul-85 10:05:54 EDT
Reply-To: std-unix-request@ut-sally
Organization: MCC (Austin, TX)
Lines: 37
Approved: jbc@mcc-db.UUCP

From: John Chambers (guest moderator) 

Topic: getopt and command line arguments continued

----------------------------------------------------------------------

Date: Wed, 10 Jul 85 09:53:45 EDT
From: seismo!elsie!ado@ut-sally.ARPA
Subject: getopt bundling brouhaha

Why all this brouhaha over whether or not getopt should allow option arguments
to be bundled with option names?  Let each user decide! People who wanted to
bundle could place commands such as

	GETOPT=b
	export GETOPT

in their login command files; getopt could check the GETOPT environment
variable to see if it contained a 'b' and allow bundling if it did.

This method could be used to give users control over other aspects of
getopt's behavior (whether to be sensitive to the case of option names;
whether to recognize options anywhere on the command line; and so on).
--
	UUCP: ..decvax!seismo!elsie!ado    ARPA: elsie!ado@seismo.ARPA
	DEC, VAX and Elsie are Digital Equipment and Borden trademarks



----------------------------------------------------------------------

-- 

John B. Chambers, Microelectronics and Computer Technology Corp., Austin, TX
{ihnp4,seismo,ctvax}!ut-sally!mcc-db!jbc, jbc@ut-sally.ARPA, chambers@mcc.ARPA