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: Robert Dodier <robert.dodier@gm...> - 2006-08-06 16:43:49
I am using SBCL 0.9.9 on Linux.
I find that (compile-file-pathname "/tmp/t.lisp" :output-file "t") =>
and (compile-file "/tmp/t.lisp" :output-file "t") clobbers /tmp/t.lisp
with the fasl output.
>From what I can tell the behavior of compile-file-pathname and compile-file
wrt output filenames is allowed to be implementation dependent by the CLHS,
but choosing the same name for the output file as the input file seems like
a weak choice. Surely /tmp/t.fasl would be better in the above examples?
Thanks for your attention to this problem.
"Robert Dodier" <robert.dodier@...> writes:
> I find that (compile-file-pathname "/tmp/t.lisp" :output-file "t") =>
> and (compile-file "/tmp/t.lisp" :output-file "t") clobbers /tmp/t.lisp
> with the fasl output.
Fixed in 0.9.15.25, thanks for the report!
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."