unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
Cc: guile-devel@gnu.org
Subject: Re: memoization and conditional defines
Date: Thu, 7 Nov 2002 15:54:19 -0500	[thread overview]
Message-ID: <200211071554.19549.clinton@unknownlamer.org> (raw)
In-Reply-To: <3DCABA28.3421DA63@pacbell.net>

> I don't care how memoization works.  I understand there are
> optimization issues.  Optimizing isn't important to me, or
> I would not use an interpretive language as my "extension
> language".  If you add a disabling mechanism, then you'll
> have the best of all worlds.  You can memoize/optimize to
> your heart's content, and I'll disable it for my purposes.
> If that is not practical and Guile becomes, essentially,
> an semi-compiled language with constraints on where
> defines may happen, then my goose will be cooked.

Not to mention how Guile wouldn't be Scheme anymore. Why can't code be 
memiozied and compiled incrementally?

-- 
http://unknownlamer.org
Truth lies in loneliness
When hope is long gone by


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


  reply	other threads:[~2002-11-07 20:54 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 [this message]
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

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=200211071554.19549.clinton@unknownlamer.org \
    --to=clinton@unknownlamer.org \
    --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).