From: Bruce Korb <bkorb@pacbell.net>
Cc: Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>, guile-devel@gnu.org
Subject: Re: memoization and conditional defines
Date: Sun, 17 Nov 2002 13:42:19 -0800 [thread overview]
Message-ID: <3DD80D3B.AE5B9F56@pacbell.net> (raw)
In-Reply-To: 87y97slyip.fsf@zagadka.ping.de
Marius Vollmer wrote:
>
> Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
>
> > I would again like to put your focus on the question, whether we should
> > support top level forms like the following:
> >
> > (if <condition> (define foo bar))
>
> I'd say that we might want to allow this, but don't try to make it
> behave especially nice.
viz: (if <condition> (eval '(define foo bar)))
Yes?
> We should provide a better alternative,
> however: Conditional 'defines' should be decided at compile time, not
> at run-time. We might extend 'cond-expand' to allow running arbitrary
> code, or something in that direction.
For me, either/anything is fine. I just have to be able
to accomplish it in some fashion. The required syntax
is less interesting.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-11-17 21:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 17:52 memoization and conditional defines Dirk Herrmann
2002-11-07 19:08 ` Bruce Korb
2002-11-07 20:54 ` Clinton Ebadi
2002-11-07 23:22 ` Lynn Winebarger
2002-11-08 0:46 ` Bruce Korb
2002-11-08 1:24 ` Lynn Winebarger
2002-11-09 8:19 ` Dirk Herrmann
2002-11-09 22:39 ` Bruce Korb
2002-11-08 3:11 ` Rob Browning
2002-11-09 9:00 ` Dirk Herrmann
2002-11-09 9:41 ` tomas
2002-11-09 17:08 ` Rob Browning
2002-11-17 20:41 ` Marius Vollmer
2002-11-17 21:42 ` Bruce Korb [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=3DD80D3B.AE5B9F56@pacbell.net \
--to=bkorb@pacbell.net \
--cc=dirk@sallust.ida.ing.tu-bs.de \
--cc=guile-devel@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).