From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: vm merged to master
Date: Mon, 16 Mar 2009 23:54:48 +0100 [thread overview]
Message-ID: <m3myblrscn.fsf@pobox.com> (raw)
In-Reply-To: <87vdqcqihv.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 14 Mar 2009 15:36:12 +0100")
Heya Ludo,
On Sat 14 Mar 2009 15:36, ludo@gnu.org (Ludovic Courtès) writes:
>> `(procedure-property apply 'arity)' needs some work
>
> Right, that won't work if `apply' is a program. The question is: what
> should we do with procedure properties?
You jump questions ;)
1) Procedure properties do work on programs. They just aren't
serialized to disk. But some serializations set properties on the
resulting procedure -- e.g. define*.
2) Programs do have properties -- program-properties, i think the
accessor is.
3) Should arity be accessed via procedure-properties? I think not.
Logically properties are cached values, not computed values, whereas
arity can be computed.
3.5) Should arity even be represented like that? The recent addition to
(ice-9 session), procedure-arguments, is another take on that
question.
4) For some reason I like numbered lists recently? Please take it as
some way of organizing my thoughts, it's not intended to be pedantic
;)
> Before the VM, [procedure-properties] could be used both with subrs
> and Scheme closures.
They still can.
> - the `object-ref' limitation to 256 objects;
We spoke of this on IRC, for those that weren't there. Actually, for
those that don't know: #guile is a friendly place. We actually have a
night shift going during the week, if you drop in between 21h and 24h
CET, people are likely hacking away :-)
> - `current-reader' not taken into account;
I want to fix this soon.
> - circular references among modules (previously worked around via
> autoloads) not supported---but this is a good thing, it's an
> opportunity to remove kludges. :-)
Is this really the case? Can you make a test case?
> I'll eventually proceed with the merge in the BDW-GC branches.
Great, I'm looking forward to that :-))
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-03-16 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 23:04 vm merged to master Andy Wingo
2009-03-14 13:19 ` Neil Jerram
2009-03-16 22:48 ` Andy Wingo
2009-03-19 0:51 ` Neil Jerram
2009-03-14 14:36 ` Ludovic Courtès
2009-03-16 22:54 ` Andy Wingo [this message]
2009-03-15 0:01 ` Greg Troxel
2009-03-16 21:53 ` 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=m3myblrscn.fsf@pobox.com \
--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).