🚀 go-pugleaf

yarnall@opusc.csd.scarolina.edu (Ken Yarnall) writes:

>In article <15839@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>+In article <1990Nov13.125723.8271@opusc.csd.scarolina.edu> yarnall@opusc.csd.scarolina.edu (Ken Yarnall) writes:
>+>In article <7594.273e8c18@jetson.uh.edu> honp9@jetson.uh.edu (Jason L. Tibbitts III) writes:
>+>
>+>+Do the pattern-matching functions in 2.0 require the parenthesis grouping?
>+>
>+>Definitely not.
>+
>+	Uh, I advise trying it before saying that.  A current "bug" in the

Well, here I have a 3000 with 2.0. (ks 36.207) In my C.D. I have a file called
 "rmfunny.c" and "leak.c"
 I type ` list rmfunny.c|leak.c' and it says
	`No imformation for "rmfunny.c|leak.c": object not found'

Also I have some files ending in 'c' and in 'p', typeing
      ' list #?.c|p' lists NO files at all, but
      ' list #?.(c|p)' DOES work.

So, what do you think? Are they required? I think so.

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.

Besides sovling the ambiguity problem, spaces make things READABLE.