From: Matt Wette <matthew.wette@verizon.net>
To: guile-user@gnu.org
Subject: Re: eval-when not giving me what I hoped for
Date: Thu, 11 Feb 2016 05:47:55 -0800 [thread overview]
Message-ID: <5E1E9068-244D-4B86-97AD-6D9106432A50@verizon.net> (raw)
In-Reply-To: <CAGua6m3kjMjhu_BZUbsnkwrw5DDYHDtn7eVuhNzyBZ5Tb63WSg@mail.gmail.com>
> On Feb 11, 2016, at 1:37 AM, Stefan Israelsson Tampe <stefan.itampe@gmail.com> wrote:
>
> the result of eval-when will be available only att specified phases. So your eval-when code will not be available
> except at expansion. Also it looks like you want to precompile the regexes. This is not a stupid idea and should
> be done at load time because regexp literals is not supported by guile scheme.
>
There is a load option to eval-when. I can try that but I need to think about how to test it. — Matt
prev parent reply other threads:[~2016-02-11 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 4:28 eval-when not giving me what I hoped for Matt Wette
2016-02-11 9:37 ` Stefan Israelsson Tampe
2016-02-11 10:08 ` Stefan Israelsson Tampe
2016-02-11 10:09 ` Stefan Israelsson Tampe
2016-02-11 13:47 ` Matt Wette [this message]
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=5E1E9068-244D-4B86-97AD-6D9106432A50@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).