From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel Subject: Re: bug in syncase Date: 24 Nov 2002 09:25:14 +0000 Sender: guile-devel-admin@gnu.org Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1038132630 22423 80.91.224.249 (24 Nov 2002 10:10:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 24 Nov 2002 10:10:30 +0000 (UTC) Cc: Guile Development Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18Ftib-0005pE-00 for ; Sun, 24 Nov 2002 11:10:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 18FtjG-0006M6-00; Sun, 24 Nov 2002 05:11:06 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 18Ftiu-0005oF-00 for guile-devel@gnu.org; Sun, 24 Nov 2002 05:10:44 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 18Ftip-0005cl-00 for guile-devel@gnu.org; Sun, 24 Nov 2002 05:10:42 -0500 Original-Received: from mail.uklinux.net ([80.84.72.21] helo=s1.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.10) id 18Ftip-0005Z1-00 for guile-devel@gnu.org; Sun, 24 Nov 2002 05:10:39 -0500 Original-Received: from laruns.ossau.uklinux.net (bts-0978.dialup.zetnet.co.uk [194.247.51.210]) by s1.uklinux.net (8.11.6/8.11.6) with ESMTP id gAOAAal22143; Sun, 24 Nov 2002 10:10:36 GMT Original-Received: from laruns.ossau.uklinux.net.ossau.uklinux.net (localhost [127.0.0.1]) by laruns.ossau.uklinux.net (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id 39F14DC12B; Sun, 24 Nov 2002 09:25:15 +0000 (GMT) Original-To: Dirk Herrmann In-Reply-To: Original-Lines: 33 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:1746 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:1746 >>>>> "Dirk" == Dirk Herrmann 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