[bug #30169] Auto-compilation failure of a module doesn't lead to a failure [1.9.11]

[Andy Wingo]

Follow-up Comment #2, bug #30169 (project guile):

You know, we might consider this to be the same problem as we see here:

$ guile -L .
scheme@(guile-user)> (use-modules (foo))
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-autocompile argument to disable.
;;; compiling /tmp/foo.scm
;;; WARNING: compilation of /tmp/foo.scm failed:
;;; key read-error, throw args ("scm_i_lreadparen" "/tmp/foo.scm:3:1: end of
file" () #f)
Throw to key `read-error':
ERROR: In procedure scm_i_lreadparen:
ERROR: /tmp/foo.scm:3:1: end of file
Entering the debugger. Type `bt' for a backtrace or `c' to continue.
0 debug> c
ERROR: In procedure scm_i_lreadparen:
ERROR: /tmp/foo.scm:3:1: end of file
scheme@(guile-user)> (use-modules (foo))
scheme@(guile-user)> 

The second (use-modules (foo)) should not succeed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30169>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/