From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: illegal uses of define in guile
Date: Mon, 21 Oct 2002 12:04:37 +0200 [thread overview]
Message-ID: <20021021100437.GB8559@www> (raw)
In-Reply-To: <Pine.GSO.4.05.10210191706040.10707-100000@sallust.ida.ing.tu-bs.de>
On Sat, Oct 19, 2002 at 05:22:03PM +0200, Dirk Herrmann wrote:
[...]
> Summarized:
> * The compiler must be able to emit code that allows references to
> identifiers to be looked up at use time (that is, in the executor).
> * The executor must be able to handle definitions.
> * Once a binding has been referenced, the binding should not change.
Is this going to be enforced at run time somehow (says he with a
little evil grin) -- or does a change on an once-referenced binding
result in undefined behaviour?
In the first case there could be a hook for those interested in
`fixing' the memoization. Then you would have the best of both
worlds -- paying an extra penalty if you decide to do quirky
things. In the second case, well...
Thinking about it, even this is something the compiler could
emit optionally.
(Don't take my rants too serioulsy though -- I'm far from actually
playing around with the compiler).
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-21 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 15:22 illegal uses of define in guile Dirk Herrmann
2002-10-19 15:44 ` Marius Vollmer
2002-10-21 10:04 ` tomas [this message]
2002-11-03 16:28 ` Marius Vollmer
2002-11-04 10:21 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 17:17 Dirk Herrmann
2002-10-14 17:49 ` Bruce Korb
2002-10-14 19:42 ` Neil Jerram
2002-10-15 0:18 ` Bruce Korb
2002-10-15 6:15 ` Dirk Herrmann
2002-10-15 10:49 ` tomas
2002-10-15 13:33 ` rm
2002-10-15 13:58 ` Bruce Korb
2002-10-15 12:45 ` rm
2002-10-18 21:55 ` Marius Vollmer
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=20021021100437.GB8559@www \
--to=tomas@fabula.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).