On Thu, Oct 11, 2012 at 11:23:22PM -0500, Evan Hanson wrote: > This patch fixes ticket #928, where compiling from standard input > ignores the user-specified -output-file name, if given.
I approve of this patch; attached is a signed-off copy. The next core maintainer to approve may also sign off and push it, as per our protocol. (am I doing this right?) Thanks for your contribution, Evan! As an aside: what's the rationale for naming the executable "a"? a.out seems more typical under UNIX. No idea what typical Windows-compilers do. Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth
>From 407fc82c5768162946b50e1722d094fdcf00d6f2 Mon Sep 17 00:00:00 2001 From: Evan Hanson <[email protected]> Date: Thu, 11 Oct 2012 22:31:36 -0500 Subject: [PATCH] respect -output-file option when compiling from stdin Signed-off-by: Peter Bex <[email protected]> --- csc.scm | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/csc.scm b/csc.scm index b0a94b4..b067c4e 100644 --- a/csc.scm +++ b/csc.scm @@ -728,8 +728,9 @@ EOF (set! rest (cdr rest)) ] [(-host) #f] [(-) - (set! target-filename (make-pathname #f "a" executable-extension)) - (set! scheme-files (append scheme-files '("-")))] + (set! scheme-files (append scheme-files '("-"))) + (unless target-filename + (set! target-filename (make-pathname #f "a" executable-extension)))] [else (when (eq? s '-to-stdout) (set! to-stdout #t) -- 1.7.9.1
_______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
