Path: utzoo!attcan!uunet!samsung!usc!apple!agate!violet.berkeley.edu!pete
From: pete@violet.berkeley.edu (Pete Goodeve)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <1990Nov6.075223.29417@agate.berkeley.edu>
Date: 6 Nov 90 07:52:23 GMT
References: <1990Nov4.054222.24999@agate.berkeley.edu> <6984@sugar.hackercorp.com> <1990Nov4.215000.2760@opusc.csd.scarolina.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 29


In  <2188@lpami.wimsey.bc.ca> (4 Nov),
Larry Phillips (lphillips@lpami.wimsey.bc.ca) writes:
>  Since the '|' is already in use in regular expressions, overloading it for
> pipes seems to me to be preferable to using another character and making it
> special too.

A pertinent point.


In  <1990Nov5.021744.3349@opusc.csd.scarolina.edu> (5 Nov),
Ken Yarnall (yarnall@opusc.csd.scarolina.edu) writes:
> Making the idiot user include whitespace or not seems to be an awkward way of
> handling it, to me.  How do I remember if I should throw a space in, of if it
> isn't allowed?   [.......]                                   Seems to
> me that in any `modern' command-line interface, enforcing the amount of
> whitespace between tokens is clumsy ("In columns 1-10 appear the command
> name.  Column 12 contains the optional redirection symbol `<'.  If
> present...")
But it's not really like that is it? Separatingtokenswithwhitespaceissometh
ingwedoallthetime.  EXTRA white space shouldn't be prohibited, naturally,
but I don't see any problem in requiring it in reasonably obvious places.

                                    -- Pete --

[and for those who still advocate the C-Shell style, herewith a
quote from the BUGS: section of the man pages for csh:

    "Quoting conventions are contradictory and confusing."            ]