From: ludo@chbouib.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Evaluator cleanup
Date: Sat, 24 Feb 2007 17:24:49 +0100 [thread overview]
Message-ID: <87irdrplpq.fsf@chbouib.org> (raw)
Hi,
I have a patch that further "despaghettifies" the evaluator, as Han-Wen
would say. ;-) It adds two files, `eval-memoize.i.c' and
`eval-unmemoize.i.c', and moves memoizers in the former and unmemoizers
in the latter. Thus, the functions that end up in these files are:
* `eval-memoize.i.c'
c_improper_memq, canonicalize_define, memoize_as_thunk_prototype,
m_body, m_expand_body, scm_m_begin, scm_m_case, scm_m_cond,
scm_m_define, scm_m_delay, scm_m_future, scm_m_do, scm_m_if,
scm_m_lambda, check_bindings, transform_bindings, memoize_named_let,
scm_m_let, scm_m_letrec, scm_m_letstar, scm_m_and, scm_m_or, iqq,
scm_m_quasiquote, scm_m_quote, scm_m_set_x, scm_m_apply,
scm_m_atbind, scm_m_cont, scm_m_at_call_with_values,
scm_m_generalized_set_x, scm_m_atslot_ref, scm_m_atslot_set_x,
scm_m_nil_cond, scm_m_atfop, scm_m_expand_body, scm_m_undefine,
scm_macroexp
* `eval-unmemoize.i.c'
unmemoize_expression, unmemoize_exprs, unmemoize_and,
unmemoize_begin, unmemoize_case, unmemoize_cond, unmemoize_delay,
unmemoize_do, unmemoize_if, unmemoize_lambda, build_binding_list,
unmemoize_let, unmemoize_letrec, unmemoize_letstar, unmemoize_or,
unmemoize_quote, unmemoize_set_x, unmemoize_apply,
unmemoize_atcall_cc, unmemoize_at_call_with_values,
unmemoize_future, unmemoize_atslot_ref, unmemoize_atslot_set_x,
unmemoize_builtin_macro, scm_i_unmemocopy_expr,
scm_i_unmemocopy_body, scm_unmemocar
It does nothing beside this, so it should be harmless. Ok to commit?
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2007-02-24 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 16:24 Ludovic Courtès [this message]
2007-02-24 22:31 ` Evaluator cleanup Neil Jerram
2007-02-25 8:57 ` Ludovic Courtès
2007-02-25 9:05 ` Ludovic Courtès
2007-02-25 14:21 ` Han-Wen Nienhuys
2007-02-25 22:32 ` Kevin Ryde
2007-02-26 20:04 ` Neil Jerram
2007-02-27 8:17 ` Ludovic Courtès
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=87irdrplpq.fsf@chbouib.org \
--to=ludo@chbouib.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).