From: Matt Wette <matthew.wette@verizon.net>
To: guile-user@gnu.org
Subject: how far does eval go when module gets compiled?
Date: Mon, 11 Jan 2016 20:52:19 -0800 [thread overview]
Message-ID: <5D0F53B9-039A-440D-BA67-CBD02F4820AE@verizon.net> (raw)
When a module is compiled to generate a .go file is it possible to know (predict) what will be evaluated?
For example
(define-module (foo) #:export (bar))
(define bar (+ 3 4))
Is the “+” executed at compile time or at load time?
Matt
next reply other threads:[~2016-01-12 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 4:52 Matt Wette [this message]
2016-01-12 7:56 ` how far does eval go when module gets compiled? Taylan Ulrich Bayırlı/Kammer
2016-01-12 19:52 ` Ludovic Courtès
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=5D0F53B9-039A-440D-BA67-CBD02F4820AE@verizon.net \
--to=matthew.wette@verizon.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).