Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!rutgers!cbmvax!cbmehq!cbmger!peterk
From: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Pipes
Message-ID: <579@cbmger.UUCP>
Date: 16 Nov 90 16:36:20 GMT
References: <7594.273e8c18@jetson.uh.edu> <1990Nov13.125723.8271@opusc.csd.scarolina.edu> <15839@cbmvax.commodore.com> <1990Nov14.192153.12963@opusc.csd.scarolina.edu> <1990Nov15.163126.7290@msuinfo.cl.msu.edu>
Reply-To: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Organization: Commodore Bueromaschinen GmbH, West Germany
Lines: 21

In article <1990Nov15.163126.7290@msuinfo.cl.msu.edu> jap@convex.cl.msu.edu (Joe Porkka) writes:
>
>Even if not, WHAT IS THE BIG DEAL WITH FORCING SPACES BEFORE (AND/OR AFTER) THE
>| to indicate pipes? Then there is no problems with parsing, since spaces
>in filenames are REQUIRED to be in quotes, and the | would be
>REQUIRED to NOT be enclosed in the quotes with the filename.
>
>People who complain about having to type extra spacing probably grew
>up on BASIC and still like it.
                                 Nah, nah.
>
>Besides sovling the ambiguity problem, spaces make things READABLE.

I agree fully, but why do you mention BASIC? I belong to the crowd that
used BASIC heavily on our PETs and CBMs and there the parser was so
intelligent that you didn't need spaces! Only with the upcome of the
"so intelligent" PCs we had to go back to spaces, sigh.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk