🚀 go-pugleaf

In article <23494@usc.edu> addison@pollux.usc.edu (Richard Addison) writes:
>In article <10142@cbmvax.commodore.com> daveh@cbmvax (Dave Haynie) writes:
>>or the command doesn't have built-in expansion (like ZOO under AmigaDOS).

>Nitpick:  ZOO has some built-in expansion.  That is, it will match a
>wildcard against a filename but not against a directory name.  Thus, all
>subdirectories have to be explicitly specified:  subdir/*.   Yes, I
>know, this can be a pain for ZOOing a directory with a lot of branches,
>especially if they go several levels down.

Nitpick back at ya: under AmigaDOS, "*" isn't a wildcard.  In any case,
it sounds like part of the problem with programs accepting wildcards in
general: it takes work on the part of the programmer.  Some of the 
compilers out there have very simple-minded pattern matching functions;
probably where ZOO got it's "*".  Under UNIX, the shell expands the 
wildcards, so that's not really a problem with UNIX zoo (though UNIX
runs into a different problem -- the normal command-line buffer is too
short for many of the multi-level archives I've built.  That's a good
argument for program expansion vs. shell expansion in this case).

>That is, it thrashes around for quite a while before getting down to
>business.  Now, if I CD Ram: first and then try:

>	ZOO v DH0:BigDir/foo.zoo

>it does not thrash around.  Why?

It sure sounds like it's creating some temporary files in the current
directory, which is probably a UNIX-ism.  It would work better in the 
general case if, when making temporary files, it put them in "T:", the
proper place for temporary files on the Amiga.

>--Rich


-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
                    Too much of everything is just enough