From: Jean Abou Samra <jean@abou-samra.fr>
To: guile-user@gnu.org
Subject: Auto-compilation and the REPL
Date: Sun, 27 Jun 2021 00:04:04 +0200 [thread overview]
Message-ID: <daebe80a-e95c-3737-03b2-f4184700781f@abou-samra.fr> (raw)
Hello,
It seems that Guile always compiles the code
entered at the REPL even with --no-auto-compile:
jean@laptop-jean:~/repos/lilypond$ guile --no-auto-compile
GNU Guile 3.0.5.130-5a1e7
[Copyright notices...]
scheme@(guile-user)> (nonexistent-procedure)
;;; <stdin>:1:1: warning: possibly unbound variable `nonexistent-procedure'
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Unbound variable: nonexistent-procedure
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
The ;;; <stdin> warning is the same as when compiling this
code in a script.
Is this expected? I couldn't find anything about it in the
documentation.
Thanks,
Jean Abou Samra
next reply other threads:[~2021-06-26 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 22:04 Jean Abou Samra [this message]
2021-07-03 15:38 ` Auto-compilation and the REPL Jean Abou Samra
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=daebe80a-e95c-3737-03b2-f4184700781f@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@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).