unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>,
	Guile Development <guile-devel@gnu.org>
Subject: Re: bug in syncase
Date: Tue, 03 Dec 2002 19:12:26 -0600	[thread overview]
Message-ID: <87znrmh9j9.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3bs4f5ngl.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "24 Nov 2002 09:25:14 +0000")

Neil Jerram <neil@ossau.uklinux.net> writes:

> - I dislike explicit uses of eval, so would prefer not to have to
> use such an approach.

Though I tend to agree, and though it may not apply here, I'd like to
try to make sure we all consider whether or not the way guile has
handled things up to now may have hidden a bunch of operations that
are more or less equivalent to using eval.  In such cases (personally
speaking) I'd probably rather just see an explicit eval.

> - Looking at the analogous example in Scheme, have we agreed
> (definitively) that Guile should _not_ detect the redefinition and
> rememoize accordingly?

I'm not sure -- it might be nice if the guile interpreter was smart
enough to detect and handle such things if the costs (in code,
performance, and time complexity) aren't too high when running
interactively.

However, I'd like to try not to require things of *non-interactive*
sessions that are at odds with extremely efficient offline
compilation, a situation where separating the expansion environment
from the evaluation environment is likely to be fairly important to
good performance.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-12-04  1:12 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
2002-11-24 10:33           ` Dirk Herrmann
2002-12-04  1:12           ` Rob Browning [this message]
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=87znrmh9j9.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --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).