URL:
<http://savannah.gnu.org/bugs/?30169>
Summary: Auto-compilation failure of a module doesn't lead
to a failure [1.9.11]
Project: Guile
Submitted by: civodul
Submitted on: Thu 17 Jun 2010 01:06:37 PM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Consider this example, where auto-compilation of (foo) fails:
#v+
$ cat foo.scm
(define-module (foo))
(open
$ cat bar.scm
(use-modules (foo))
(display "hello!\n")
$ guile -L . bar.scm
;;; note: source file bar.scm
;;; newer than compiled
/home/ludo/.cache/guile/ccache/2.0-0.R-LE-8/home/ludo/src/guile/bar.scm.go
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-autocompile argument to disable.
;;; compiling bar.scm
;;; compiling ./foo.scm
;;; WARNING: compilation of ./foo.scm failed:
;;; key read-error, throw args ("scm_i_lreadparen" "./foo.scm:3:1: end of
file" () #f)
;;; WARNING: compilation of bar.scm failed:
;;; key read-error, throw_args ("scm_i_lreadparen" "./foo.scm:3:1: end of
file" () #f)
hello!
$ echo $?
0
#v-
Guile should instead abort as soon as auto-compilation fails.
Thanks,
Ludo'.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30169>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
