Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!agate!tornado.Berkeley.EDU!asun
From: asun@tornado.Berkeley.EDU (a sun)
Newsgroups: comp.arch
Subject: Re: UNIX mind-set  -> OK, OK!
Message-ID: <1991Jan14.074100.9652@agate.berkeley.edu>
Date: 14 Jan 91 07:41:00 GMT
References: <11305@lanl.gov> <1991Jan14.013815.11419@ims.alaska.edu> <11314@lanl.gov>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Followup-To: alt.religion.computers
Organization: Celestial Manifestations Inc.
Lines: 27

In article <11314@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
>
>Yes, both of the shells that are bundled with versions of UNIX _do_
>automatically trash (that is, 'process') the command line arguments to
>expand wildcards.  Explains why I don't use the bundled command shells
>much.  This is a choice that _should_ be left to the discretion of the
>utility writer.
>

Sorry, but you're wrong here also.
You'll notice (an example which was given in a previous post)
	echo "*" and 
	echo *
give different results. 

The expansion of wildcards is left to the user's discretion, which I
think is appropriate. It provides an interface that is consistent and
easily tailered to the user's needs. I suggest you read csh(1) and
sh(1) before commenting further on the inadequacies of the standard
shells.

If you really don't want any filename expansions whatsoever, just "set
noglob."

-----
a sun
(this doesn't belong in comp.arch)