Issue: PATHNAME-WILD (Version 2)

[Richard Mlynarik <MLY@AI.AI.MIT.EDU>]

      The CL pathname model does not provide a way to represent such wildcards,
      which means, for example, that (MAKE-PATHNAME :NAME "F*O") cannot be
      recognized by portable code as containing a wildcard.

This is not even `portable' code for creating a wildcarded pathname.
How do you distinguish between pathname named "f*o" and a wildcarded
pathname which starts with an #\f and ends with an #\o??  (BTW, the
Symbolics pathname system ducks the entire issue.)

The pathname specification is so crippled that adding dinky frobs like
PATHNAME-WILD-P isn't going to make any difference to `portability' --
about all it will add is another page to the CL manual.