From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-8-23-gea6b18e
Date: Sat, 17 Jul 2010 12:12:13 +0200 [thread overview]
Message-ID: <m38w5a5sea.fsf@unquote.localdomain> (raw)
In-Reply-To: <874ol12gj7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 28 Feb 2010 22:31:56 +0100")
Heya,
On Sun 28 Feb 2010 22:31, ludo@gnu.org (Ludovic Courtès) writes:
> (Sorry for the late & light review...)
Sorry for the late & light reply :)
>> +#define SCM_I_FLUID_P(x) (!SCM_IMP (x) && SCM_TYP7 (x) == scm_tc7_fluid)
>
> How about renaming it to ‘SCM_FLUID_P’ and making it public?
Done
>> +#define SCM_I_FLUID_NUM(x) ((size_t)SCM_CELL_WORD_1(x))
>
> Could be in #ifdef BUILDING_LIBGUILE?
Done
>> diff --git a/libguile/vm-engine.c b/libguile/vm-engine.c
>> index 75dd613..5d1e1d6 100644
>> --- a/libguile/vm-engine.c
>> +++ b/libguile/vm-engine.c
>> @@ -47,6 +47,7 @@ VM_NAME (SCM vm, SCM program, SCM *argv, int nargs)
>> SCM *objects = NULL; /* constant objects */
>> size_t object_count = 0; /* length of OBJECTS */
>> SCM *stack_limit = vp->stack_limit; /* stack limit address */
>> + SCM dynstate = SCM_I_CURRENT_THREAD->dynamic_state;
>
> Out of curiosity, what effect does this have on performance?
Dunno!
>> + (<dynref> fluid)
>> + (<dynset> fluid exp)
>
> At first sight ‘fluid-ref’ and ‘fluid-set’ would seem more natural names
> to me. What do you think?
I had it like that before, but I did it this way to match dynwind and dynlet.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-07-17 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NiTsQ-0000bX-AH@vcs-noshell.in.savannah.gnu.org>
2010-02-28 21:31 ` [Guile-commits] GNU Guile branch, master, updated. release_1-9-8-23-gea6b18e Ludovic Courtès
2010-07-17 10:12 ` Andy Wingo [this message]
2010-07-17 12:52 ` Ludovic Courtès
2010-07-18 10:24 ` Andy Wingo
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=m38w5a5sea.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@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).