Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Richard M Kreuter <kreuter@us...> - 2008-01-31 19:29:40
Update of /cvsroot/sbcl/sbcl/src/code
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv25956/src/code
220.127.116.11: Fix regression in RUN-PROGRAM when :INPUT et al. are pathnames.
* GET-DESCRIPTOR-FOR is defined with &rest, &key, and
&allow-other-keys, and one pathway passes the &rest list to OPEN. A
recent addition of a keyword argument to GET-DESCRIPTOR-FOR that
OPEN didn't recognize created a problem.
* Add test for the correct behavior.
RCS file: /cvsroot/sbcl/sbcl/src/code/run-program.lisp,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -d -r1.73 -r1.74
--- run-program.lisp 10 Jan 2008 01:48:12 -0000 1.73
+++ run-program.lisp 31 Jan 2008 19:29:25 -0000 1.74
@@ -976,7 +976,11 @@
(error "Direction must be either :INPUT or :OUTPUT, not ~S."
((or (pathnamep object) (stringp object))
- (with-open-stream (file (apply #'open object keys))
+ ;; GET-DESCRIPTOR-FOR uses &allow-other-keys, so rather
+ ;; than munge the &rest list for OPEN, just disable keyword
+ ;; validation there.
+ (with-open-stream (file (apply #'open object :allow-other-keys t
(sb-unix:unix-dup (sb-sys:fd-stream-fd file))