From: Marko Rauhamaa <marko@pacujo.net>
To: guile-user@gnu.org
Subject: Guile 2.0 interpretation vs compilation
Date: Sun, 05 Oct 2014 14:03:30 +0300 [thread overview]
Message-ID: <87d2a693st.fsf@elektro.pacujo.net> (raw)
Consider this program:
===begin test.scm=======================================================
(define (hello) #f)
(format #t "~S\n" (procedure-name hello))
(define (xyz)
(define (hello) #f)
(format #t "~S\n" (procedure-name hello)))
(xyz)
===end test.scm=========================================================
If I run:
$ guile --no-auto-compile test.scm
hello
#f
$ guile --no-auto-compile test.scm
hello
#f
$ guile test.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
[...]
hello
hello
$ guile test.scm
hello
hello
$ guile --no-auto-compile test.scm
hello
hello
# $ guile -v
guile (GNU Guile) 2.0.11
[...]
Is this a bug or expected behavior?
Marko
next reply other threads:[~2014-10-05 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 11:03 Marko Rauhamaa [this message]
2014-10-06 4:22 ` Guile 2.0 interpretation vs compilation Mark H Weaver
2014-10-06 6:33 ` Marko Rauhamaa
2014-10-06 6:52 ` Mark H Weaver
2014-10-06 7:58 ` Mark H Weaver
2014-10-06 19:05 ` Marko Rauhamaa
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=87d2a693st.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--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).