🚀 go-pugleaf

In article <1990Nov4.215000.2760@opusc.csd.scarolina.edu> yarnall@opusc.csd.scarolina.edu (Ken Yarnall) writes:
> I really dislike wildcard expansion in the shell.  Granted, it would have
> been nicer in 1.3, since there was no library support of standard pattern
> matching, but now that 2.0 has good, standardized routines to do this, I
> can't for the life of me see how shell expansion is superior.

(a) There are still machines outthere running 1.3. Like, most of them.
(b) You still need quoting conventions. Quickly, how do you delete a file
    named "#?.c"? Why not use them consistently?
(c) You're at the mercy of programmers who neglect to provide for it. VAX/VMS
    has had wildcard libraries forever, and it still trips me up. That's how
    you get files named "#?.c" in the first place.

For things like "move", I'd rather go to slices:

	move {.*}.c \1.h

You know, like in regular expressions...
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.