From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andy Wingo" <wingo@pobox.com>,
bug-guile@gnu.org
Subject: [bug #30169] Auto-compilation failure of a module doesn't lead to a failure [1.9.11]
Date: Fri, 25 Jun 2010 15:29:27 +0000 [thread overview]
Message-ID: <20100625-152926.sv20118.32167@savannah.gnu.org> (raw)
In-Reply-To: <20100620-142300.sv15145.70745@savannah.gnu.org>
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/
prev parent reply other threads:[~2010-06-25 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:06 [bug #30169] Auto-compilation failure of a module doesn't lead to a failure [1.9.11] Ludovic Courtès
2010-06-18 8:32 ` Andy Wingo
2010-06-18 14:52 ` Ludovic Courtès
2010-06-18 17:03 ` Andy Wingo
2010-06-20 14:23 ` Ludovic Courtès
2010-06-20 20:19 ` Andy Wingo
2010-06-25 15:29 ` Andy Wingo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100625-152926.sv20118.32167@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).