From: "Ludovic Courtès" <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, bug-guile@gnu.org
Subject: [bug #30169] Auto-compilation failure of a module doesn't lead to a failure [1.9.11]
Date: Sun, 20 Jun 2010 14:23:00 +0000 [thread overview]
Message-ID: <20100620-142300.sv15145.70745@savannah.gnu.org> (raw)
In-Reply-To: <20100617-130637.sv15145.59405@savannah.gnu.org>
Follow-up Comment #1, bug #30169 (project guile):
(Follow-up from bug-guile.)
Andy says:
> Some files may be interpreted, but fail to compile.
OK.
[...]
> So, you want Guile to fail faster for this error; how do you distinguish
> it from eval-when errors as above? Or would you prefer that eval-when
> errors lead to failures as well?
Do you mean that, for programs written to be interpreted, which lack proper
‘eval-when’ clauses, the idea was to fall back to interpretation when
auto-compilation fails? That would indeed be friendlier to programs written
for previous versions of Guile.
However, in the example I gave, somehow, an error should occur. With 1.8 you
would get an error when reading ‘foo.scm’, whereas here it’s just
silently ignored, which sounds wrong.
Ludo'.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30169>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-06-20 14:23 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 [this message]
2010-06-20 20:19 ` Andy Wingo
2010-06-25 15:29 ` Andy Wingo
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=20100620-142300.sv15145.70745@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
/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).