From: "Marco Maggi" <marco.maggi-ipsu@poste.it>
To: "ludo" <ludo@gnu.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: compiled closures status
Date: Tue, 27 Nov 2007 21:37:36 +0100 [thread overview]
Message-ID: <JS6MMO$7A1E30CAAEAB4F170D4446C3E7EFC9EB@poste.it> (raw)
Ciao,
"Ludovic Courtès" wrote:
>
>"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:
>
>> I have written a simple extension to test the
>> compiled closures feature, and it seems to work.
>> I wonder if it can be documented (and in this case
>> I can contribute a Texinfo node) or there are plans
>> to change the API.
>
>You're referring to `scm_makcclo ()' and the likes?
Yes.
>The difference with `scm_closure ()', AIUI, is that a cclo's
>environment is a simple C array instead of an alist.
Mh. The "env" parameter is a simple alist? I will try to
find what is the "code" one.... but I doubt that it is a
gsubr. The compiled closure is the pair "scm_t_bits"
array/gsubr.
>However, I'm under the impression that code in `eval.c'
>doesn't know how to deal with a cclo's environment
>(e.g., there is no occurrence of `SCM_CCLO_BASE ()').
In Guile 1.8.3 at line 4139 of "eval.c",
| case scm_tc7_cclo:
| arg1 = proc;
| proc = SCM_CCLO_SUBR (proc);
which means that the compiled procedure is invoked with
the closure itself as first argument.
>So, what makes you think it works? :-)
I tried it:
$ tla register-archive http://arch.gna.org/gee/gee-2007
$ tla get <the-archive>/gee-examples--devel--0.4
:-)
--
Marco Maggi
"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2007-11-27 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 20:37 Marco Maggi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-27 6:59 compiled closures status Marco Maggi
2007-11-27 9:12 ` 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='JS6MMO$7A1E30CAAEAB4F170D4446C3E7EFC9EB@poste.it' \
--to=marco.maggi-ipsu@poste.it \
--cc=guile-user@gnu.org \
--cc=ludo@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).