* bug#50060: The REPL does not honor --no-auto-compile
@ 2021-08-14 19:41 Jean Abou Samra
0 siblings, 0 replies; only message in thread
From: Jean Abou Samra @ 2021-08-14 19:41 UTC (permalink / raw)
To: 50060
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.)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-08-14 19:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-14 19:41 bug#50060: The REPL does not honor --no-auto-compile Jean Abou Samra
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).