compile-file's implementation-dependent consequences

[Vincent Keunen <nrb!keunen@relay.EU.net>]

CLTL2, page 678:

X3J13 voted in June 1989 <137> to clarify that supplying a wild pathname
as the input-pathname argument to compile-file has
implementation-dependent consequences; compile-file might signal an
error, for example, or might compile all files that match the wild
pathname.


It would be nice if MCL supported the second choice.  Something like:

(defun new-compile-file (name)
  (loop for one-file in (directory name) do 
        (compile-file one-file)))


Vincent
--
Keunen Vincent                  Network Research Belgium
R&D, Software Engineer          Parc Industriel des Hauts-Sarts
keunen@nrb.be                   2e Avenue, 65
tel: +32 41 407282              B-4040 Herstal
fax: +32 41 481170              BELGIUM