From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Han-Wen Nienhuys" <hanwenn@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: unhandled constant?
Date: Fri, 31 Jan 2020 20:52:34 +0100 [thread overview]
Message-ID: <773107ff-aaf6-4b37-ba50-4ee6e30ec54c@www.fastmail.com> (raw)
In-Reply-To: <CAOw_e7Z09CYnnc1GeSfQ86HYagD0UV2m_3W0e32p9SvmjWx1mw@mail.gmail.com>
On Fri, 31 Jan 2020, at 20:17, Han-Wen Nienhuys wrote:
>
> eval-when looks like it might be a solution to the puzzle , but
> honestly, the doc at
>
> https://www.gnu.org/software/guile/manual/html_node/Eval-When.html
>
> has me mystified. When I run the example through guile 2.2 and
> display *compilation-date*,
>
> I get a different answer each time. Shouldn't it be a fixed timestamp
> (of when the compile happened?)
Yup. At least from my understanding of the documentation, but whenever I try to do eval-when I become sad so I have just decided that I am too dumb for it. Try asking in the irc channel.
next prev parent reply other threads:[~2020-01-31 19:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 23:08 unhandled constant? Han-Wen Nienhuys
2020-01-29 15:06 ` Ricardo Wurmus
2020-01-30 8:05 ` Han-Wen Nienhuys
2020-01-31 10:49 ` Han-Wen Nienhuys
2020-01-31 11:17 ` Ricardo Wurmus
2020-02-02 19:30 ` Jan Nieuwenhuizen
2020-01-31 14:57 ` Linus Björnstam
2020-01-31 15:16 ` Han-Wen Nienhuys
2020-01-31 17:50 ` Han-Wen Nienhuys
2020-01-31 18:19 ` Linus Björnstam
2020-01-31 19:17 ` Han-Wen Nienhuys
2020-01-31 19:52 ` Linus Björnstam [this message]
2020-01-31 20:01 ` Linus Björnstam
2020-02-01 9:54 ` Han-Wen Nienhuys
2020-02-01 9:56 ` Han-Wen Nienhuys
2020-02-01 10:10 ` David Kastrup
2020-02-01 11:23 ` Han-Wen Nienhuys
2020-02-01 11:36 ` David Kastrup
2020-02-01 13:12 ` Linus Björnstam
2020-02-01 11:09 ` David Kastrup
2020-02-01 13:16 ` Linus Björnstam
2020-02-01 14:23 ` David Kastrup
2020-02-01 15:21 ` Linus Björnstam
2020-02-01 21:55 ` Taylan Kammer
2020-02-01 21:58 ` Fwd: " Taylan Kammer
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=773107ff-aaf6-4b37-ba50-4ee6e30ec54c@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=guile-devel@gnu.org \
--cc=hanwenn@gmail.com \
/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).