From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: bug in syncase
Date: 24 Nov 2002 09:25:14 +0000 [thread overview]
Message-ID: <m3bs4f5ngl.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <Pine.GSO.4.05.10211231145000.25838-100000@sallust.ida.ing.tu-bs.de>
>>>>> "Dirk" == Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
Dirk> There is a mechanism in scheme that allows to prevent
Dirk> memoization: eval. If it is correct that emacs does not
Dirk> perform memoization, then it might be that the whole concept
Dirk> of the @fop memoization is wrong. Could you check whether
Dirk> it is possible to achieve emacs' behaviour by replacing the
Dirk> @fop solution by a solution based on eval (or some elisp
Dirk> equivalent of this)? I would postpone working on @fop until
Dirk> this is solved - there are still enough other things to do
Dirk> for me :-)
Is this a blocking problem for you? If it isn't, I'd say that we
don't particularly have to solve this problem now. It is only
relevant in the pathological scenario where a symbol previously
defined as a function becomes a macro, and vice versa, so it's a low
priority bug. (For example, much lower priority than the odd
behaviour of array?.)
(So we don't lose the details, I'll add a file
translation/elisp-and-memoization.text to the workbook shortly.)
For when we do solve it, here are two considerations.
- I dislike explicit uses of eval, so would prefer not to have to use
such an approach.
- Looking at the analogous example in Scheme, have we agreed
(definitively) that Guile should _not_ detect the redefinition and
rememoize accordingly?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-24 9:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.05.10211161811180.9959-100000@sallust.ida.ing.tu-bs.de>
2002-11-17 12:11 ` bug in syncase Neil Jerram
2002-11-20 17:33 ` Dirk Herrmann
2002-11-21 17:53 ` Dirk Herrmann
2002-11-21 20:22 ` Neil Jerram
2002-11-23 10:53 ` Dirk Herrmann
2002-11-24 9:25 ` Neil Jerram [this message]
2002-11-24 10:33 ` Dirk Herrmann
2002-12-04 1:12 ` Rob Browning
2002-11-23 13:01 ` Marius Vollmer
2002-12-04 18:27 ` Carl R. Witty
2002-12-04 20:54 ` Neil Jerram
2002-12-09 20:28 ` Carl R. Witty
2002-11-14 11:59 Dirk Herrmann
2002-11-15 4:10 ` Clinton Ebadi
2002-11-15 9:29 ` Lynn Winebarger
2002-11-15 9:34 ` Lynn Winebarger
2002-11-15 19:25 ` Neil Jerram
2002-11-16 18:39 ` Marius Vollmer
2002-11-17 10:54 ` Neil Jerram
2002-11-17 20:07 ` 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=m3bs4f5ngl.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).