From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from techfac.techfak.uni-bielefeld.de ([129.70.1.2]) by archone.tamu.edu with SMTP id <22531>; Mon, 9 Sep 1991 14:16:15 -0500
Received: from dahlie.TechFak.Uni-Bielefeld.DE by techfac.techfak.uni-bielefeld.de (5.65+bind 1.7+ida 1.4.2/tp.29.0890)
	id AA14154; Mon, 9 Sep 91 20:45:06 +0200
Received: by dahlie.techfak.uni-bielefeld.de (4.1/tp.29.0890)
	id AA02826; Mon, 9 Sep 91 20:45:05 +0200
Date: Mon, 9 Sep 1991 13:45:05 -0500
From: malte@techfak.uni-bielefeld.de
Message-Id: <9109091845.AA02826@dahlie.techfak.uni-bielefeld.de>
To: rc@archone.tamu.edu
Subject: Re: how to 'getopts' in rc

Today I read the first answers to my last letter on how to "getopts".
I like what John Mackin wrote, but I believe there ar two things to add:

	This is rc!  Why hamstring ourselves with old-style interfaces,

I agree with you that commandline conventions are probably not the ultimate
ones, but here at my site, there are lots of beginners and it won't make
things easier if we change that "old-style" interfaces.
And after all, I am quite comfortable with these. What says POSIX about it?

	* = ` { getopts opt1 'code1' opt2 'code2' ... - $* }

Also a good idea that didn't come to my mind! But I have lots of sh scripts
here which will occasionally be ported to rc. Your suggestion won't make
things easier.


_______________________________________________________________________________
malte@techfak.uni-bielefeld.de

send mail to:	Universitaet Bielefeld, Technische Fakultaet
		z. Hd. Malte Uhl
		Postfach 8640
		4800 Bielefeld 1