From: Jean Abou Samra <jean@abou-samra.fr>
To: 50060@debbugs.gnu.org
Subject: bug#50060: The REPL does not honor --no-auto-compile
Date: Sat, 14 Aug 2021 21:41:31 +0200 [thread overview]
Message-ID: <f2451a66-51d7-3b0f-b111-0eaad5aeb61a@abou-samra.fr> (raw)
Even when guile is run with --no-auto-compile, the
REPL still seems to be compiling the source.
$ guile --no-auto-compile
GNU Guile 3.0.5.130-5a1e7
[Legalese…]
scheme@(guile-user)> unbound-variable
;;; <stdin>:1:0: warning: possibly unbound variable `unbound-variable'
[Backtrace…]
This "possibly unbound variable" warning comes from
compilation (which can be seen by putting the same
code in a script and running with or without auto-compilation).
This is annoying, because in the REPL the code
is run immediately and we don't need the warning
about a "possibly unbound variable" just before
the actual error. In fact, it would seem desirable
to make "no auto-compilation" the default for the
REPL. Code run there is typically not
performance-sensitive.
(Originally reported at
https://lists.gnu.org/archive/html/guile-user/2021-06/msg00065.html.)
reply other threads:[~2021-08-14 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f2451a66-51d7-3b0f-b111-0eaad5aeb61a@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=50060@debbugs.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).